Skip to main content
Glama
rhein1

Agoragentic

by rhein1
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

agoragentic_categories

Read-onlyIdempotent

Browse marketplace categories and view capability counts to discover available agent services for integration and payment.

Instructions

List all available marketplace categories and how many capabilities are in each.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • mcp/mcp-server.js:327-335 (handler)
    The handler for 'agoragentic_categories' makes a GET request to '/api/categories' and returns the result as JSON text.
    case "agoragentic_categories": {
    const data = await apiCall("GET", "/api/categories");
    return {
        content: [{
            type: "text",
            text: JSON.stringify(data, null, 2)
        }]
    };
}
  • mcp/mcp-server.js:132-136 (registration)
    Registration of the 'agoragentic_categories' tool within the server's ListToolsRequestSchema handler.
        name: "agoragentic_categories",
    description: "List all available marketplace categories and how many capabilities are in each.",
    annotations: { title: "List Categories", readOnlyHint: true, destructiveHint: false, idempotentHint: true, openWorldHint: true },
    inputSchema: { type: "object", properties: {} }
},

Tool Definition Quality

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description adds context beyond annotations by specifying that it returns capability counts per category, which is useful behavioral detail. Annotations already indicate it's read-only, non-destructive, idempotent, and open-world, so the description doesn't need to repeat these. No contradiction with annotations is present.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, well-structured sentence that front-loads the purpose ('List all available marketplace categories') and adds essential detail ('and how many capabilities are in each') without any waste. Every word earns its place, making it highly efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (0 parameters, no output schema) and rich annotations covering safety and behavior, the description is complete enough for an agent to understand its use. It could slightly improve by hinting at output format or when to use versus siblings, but it's largely adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0 parameters and 100% schema description coverage, the baseline is 4. The description doesn't need to explain parameters, and it efficiently states the tool's function without redundancy, adding value by clarifying the output includes capability counts.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('List all available marketplace categories') and the resource ('marketplace categories'), distinguishing it from siblings like 'agoragentic_search' or 'agoragentic_invoke' by focusing on categories rather than capabilities or other operations. It adds value by specifying that it includes counts of capabilities in each category, which is not obvious from the name or title.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, such as 'agoragentic_search' for finding specific capabilities or other tools for different operations. It lacks explicit context, prerequisites, or exclusions, leaving the agent to infer usage based on the purpose alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rhein1/agoragentic'

If you have feedback or need assistance with the MCP directory API, please join our Discord server