Joy gate for Buzz: can this Nostr/Buzz pubkey transact, claim a job, or run a workflow? Fail-closed.
| Name | Required | Description | Default |
|---|---|---|---|
| action | Yes | transact | claim_job | run_workflow | write | Joy permission | |
| pubkey | No | Buzz/Nostr pubkey hex or npub1... | |
| agent_id | No | Optional Joy agent id |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses 'fail-closed' behavior, which is valuable context. Yet it does not describe the return format (e.g., boolean), error handling, or whether authentication is required, leaving gaps in behavioral transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence. It is front-loaded with the 'Joy gate' metaphor and reinforces fail-closed behavior, every word earning its place with no redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
There is no output schema or annotations, so the description must cover return values and edge cases. It conveys the core purpose and fail-closed policy, but does not specify the likely boolean return, invalid pubkey behavior, or the meaning of 'write' and 'Joy permission' actions. This is adequate for a simple gate but leaves actionable gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
All parameters are described in the schema (100% coverage), so the baseline is 3. The description mentions some action values but does not add meaning beyond the schema. The 'Joy permission' action remains ambiguous, and the description does not clarify parameter syntax or dependencies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly indicates this is a permission gate for Buzz, checking whether a pubkey can transact, claim a job, or run a workflow. It distinguishes itself from sibling action tools by focusing on capability checking. However, the verb is implicit ('can') rather than an explicit action like 'checks permission'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'Joy gate' implies it should be used as a pre-check before performing actions, and the listed actions hint at when to use it. However, it does not explicitly state when to use this tool versus alternatives, nor does it mention that it is a prerequisite for tools like claim_job or create_campaign.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools target distinct resources and actions. The only potential confusion is between approve_job and complete_deal, both releasing payments, but descriptions clearly differentiate job vs deal contexts. Overall, tools are well-separated.
Almost all tools follow a consistent verb_noun pattern (create_, get_, list_, etc.). The only outlier is network_stats, which lacks a verb, but this is a minor deviation from an otherwise uniform convention.
With 29 tools, the set exceeds the 25-tool threshold for a well-scoped server. While the platform covers many domains (jobs, payments, trust, identity, campaigns, tickets), the high count feels heavy and could benefit from consolidation or clearer separation into sub-modules.
Core job and stake lifecycles are fully covered, but tickets and campaigns only support create/list/get with no update, delete, or close operations. Payment also lacks a direct send/unified transfer option. These gaps are notable but workarounds exist via deals and top-up links.