Skip to main content
Glama

Pumpkin

service_get

Read-only

Get the description of an eligible service.

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>",
      "itemId": "<itemId>"
    },
    "name": "service_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesThe site ID returned by find_business.
itemIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. Beyond that the description adds nothing: it does not explain what "eligible" means, what happens when a service is ineligible, or what the returned "description" contains. For a lookup tool with no output schema, this leaves the agent guessing about the response shape.

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

Conciseness3/5

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

The single sentence is front-loaded and free of padding, which is structurally fine. But at this length the brevity reflects under-specification rather than efficiency — there is no second sentence to clarify eligibility or the return value.

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

Completeness2/5

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

With two required parameters, one of them undocumented, no output schema, and no explanation of the eligibility concept or the returned description, the definition is not complete enough for an agent to call this confidently. It should at minimum tie itemId to a service found via service_search and state what the response represents.

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

Parameters2/5

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

Schema coverage is only 50%: "site" is documented as the site ID from find_business, but "itemId" has no description in the schema, and the tool description does not clarify that it is the service identifier. The description therefore fails to compensate for the undocumented required parameter, which is the single most important thing to get right when calling this tool.

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

Purpose3/5

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

The description names a verb ("Get") and a resource ("the description of an eligible service"), so the general intent is inferable. However, "eligible" is left undefined and "description" is ambiguous — it could mean a human-readable blurb, a metadata record, or a service definition — so an agent cannot confidently distinguish this from siblings like service_search or service_estimate.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives among the many service_* siblings. The only hint is the word "eligible," which implies a precondition the description never explains. The agent must infer that this is a lookup-by-ID step following a search.

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