MCP-native agent middleware with governance enforced in code: spending limits that refuse, auditable decision provenance, and local-first Markdown memory
QMesha defines 23 tools with consistent naming (verb_noun pattern) and reasonable descriptions (avg ~120 chars). All tools have input schemas with typed parameters and descriptions. However, output schemas are not documented, critical for LLM planning. Error handling is minimal; most tools lack recovery guidance. Parameter descriptions are present but often generic (e.g., 'Optional metadata to attach to the inbox' lacks format/constraint details). No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear WRITE/READ_ONLY risk classifications. Composition is sound, tools are single-responsibility and chainable. Security: no visible credential exposure in parameters, but audit logging and permission gates are not evident in tool definitions.
Calculate revenue share distribution for a usage event.
Cancel a user's subscription (downgrades to free at period end).
Check if a user has remaining quota for a resource.
Create a new agent inbox for receiving messages.
Create a subscription intent for a user.
Create a new page in the Obsidian Wiki vault.
Find all pages that link TO the given page.
Output schemas not documented. LLMs cannot plan downstream tool calls or extract required fields (e.g., what does meter_usage return? Does it include a transaction_id for refund_payment?). This violates pattern:tool and pattern:tool-chain.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear WRITE/READ_ONLY risk classifications in metadata. LLMs cannot distinguish safe reads from destructive writes without explicit hints. Violates pattern:tool-annotation.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 68 | <=2025-11-25 | v2 |
Get current budget status for a caller.
Get the current subscription for a user.
Retrieve all messages in a conversation thread.
Retrieve usage history with optional filters.
Get all outgoing wikilinks from a page.
Run quality checks on the wiki vault.
List messages in an agent's inbox.
Record metered usage for a service call, subject to policy enforcement.
Search the Obsidian Wiki knowledge graph.
Rent an external agent to perform a task.
Rent a dedicated AgentMail inbox for an agent.
Rent a temporary council of agents for deliberation.
Rent an x402-enabled service with automatic payment.
Reset the budget for a caller.
Send a message from one agent to another.
Update a specific section within an existing wiki page.
Error handling absent. Tools lack recovery guidance (e.g., 'User not found. Try search_users() first.'). No error categorization (retryable vs user-fixable vs fatal). Violates pattern:recovery-guide and pattern:error-classification.
Parameter descriptions lack constraint details. E.g., 'metadata' is 'Optional metadata to attach to the inbox', no format, no example structure. 'max_cost_usd' lacks min/max bounds. Violates pattern:constrained-input.
lint_wiki has empty input schema (no parameters). Description is vague ('Run quality checks on the wiki vault'). Unclear what checks are performed or what output is returned. Violates pattern:tool-description.