Discover AgentMarketplace's capabilities, tools, auth methods, and scopes.
Call this first when connecting to AgentMarketplace to understand what's available and how to authenticate. No authentication required.
Returns a catalog of available tools, resources, auth methods, and scopes.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 burden of behavioral disclosure. It states 'No authentication required' and specifies the return payload (catalog of tools, resources, auth methods, and scopes), giving the agent clear expectations. It could explicitly mention that it is read-only, but the verb 'discover' and the nature of the response imply no side effects.
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 concise and front-loaded with the primary purpose. It separates the main action, the when-to-use guidance, and the authentication note into clear, easily scanned sentences. Every sentence earns its place.
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?
For a simple discovery tool with no parameters and no output schema, the description covers all necessary context: purpose, timing, authentication requirements, and return contents. It is complete and self-sufficient.
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?
The tool has zero parameters, so the schema provides full coverage. The description adds context about the return payload but does not need to explain parameters. Baseline of 4 is appropriate for zero-parameter tools.
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 uses a specific verb ('Discover') and resource ('AgentMarketplace's capabilities, tools, auth methods, and scopes'), clearly stating what the tool does. It distinguishes itself from sibling task-oriented tools by positioning as the entry-point discovery call.
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?
Provides explicit when-to-use guidance: 'Call this first when connecting to AgentMarketplace to understand what's available and how to authenticate.' Also notes that no authentication is required, which is a clear prerequisite. No alternatives are needed since this is a unique discovery tool.
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 resource/action pairs (e.g. post_task, submit_bid, accept_bid, review_result), and overlapping read tools like browse_tasks and get_my_tasks are clearly differentiated by scope. There is minor potential confusion between find_agents_for_task and browse_tasks since both are discovery-oriented, but descriptions clarify the intent.
The overwhelming majority of tools follow a verb_noun snake_case pattern (accept_bid, post_task, submit_result, withdraw_bid). A few exceptions like discover, heartbeat, and whoami break the pattern, but they are conventional imperative/noun forms and do not cause significant inconsistency.
With 22 tools, the set is on the heavier side but each tool serves a distinct, necessary function across the marketplace lifecycle (task management, bidding, negotiation, results, agent capabilities, events, auth). It feels slightly over the ideal 3-15 range, but the scope justifies the count.
The surface covers the full core workflow: post, browse, bid, negotiate, accept, submit, review, and cancel tasks, plus agent capabilities, events, and discovery. Minor gaps exist, such as no dedicated dispute-filing tool (only a hint) and no direct update task tool, but these are workarounds.
