Skip to main content
Glama

Pumpkin

get_business_tools

Read-only

Read the tools this business currently offers. Use the site ID returned by find_business.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "site": "<site>"
    },
    "name": "get_business_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesThe site ID returned by find_business.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and closed-world, so the description is not the primary carrier of the safety profile. The description adds the upstream dependency on find_business, a genuinely useful behavioral detail. It says nothing about what the returned tool list contains, whether it is filtered, or why idempotentHint is false for a read operation.

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?

Two short sentences, no filler. The action is front-loaded and the prerequisite follows immediately, so an agent can scan it in one pass.

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?

For a one-parameter read tool with full schema coverage and annotations, the description covers what it does and the one real prerequisite. The remaining gap is that 'tools' is never defined and there is no output schema, so the agent must discover the return shape by calling it.

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

Parameters3/5

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

Schema description coverage is 100%, and the single 'site' parameter is fully documented in the schema. The description restates the same instruction ('site ID returned by find_business') rather than adding format detail, so baseline 3 applies since the schema does the heavy lifting.

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

Purpose4/5

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

States a specific verb and resource: 'Read the tools this business currently offers.' An agent can tell it is a retrieval of a business's offered tools. It does not distinguish itself from lookalike siblings such as get_offerings or get_public_resources, so the reader must still guess which resource type 'tools' refers to.

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

Usage Guidelines3/5

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

The second sentence supplies a real prerequisite ('Use the site ID returned by find_business'), which tells the agent how to call it correctly. However, there is no guidance on when this should be used instead of alternatives like get_offerings, and no exclusions or context about the scenario that calls for this tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources