Skip to main content
Glama

Pumpkin

site_get

Read-only

Get this site's business overview and public contact details.

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": "site_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesThe site ID returned by find_business.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already establish this as a safe, non-destructive read, so the description only needs to add scope. It does add that only public contact details and an overview are returned, which sets expectations, but says nothing about response shape, whether the site ID can be stale, or any failure modes.

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

Conciseness4/5

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

One short, front-loaded sentence with no filler. It could be slightly sharper, since "business overview" is a vague payload promise, but nothing is wasted.

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

Completeness3/5

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

For a simple single-parameter read tool with safety covered by annotations and the parameter fully documented, the definition is minimally adequate. It stops short of describing what fields the overview or contact details actually contain, which is the main thing an agent cannot infer elsewhere without an output schema.

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?

With a single parameter at 100% schema description coverage, the schema already explains that the value is a site ID from find_business. The description adds no further meaning such as accepted formats or what happens with an unknown ID, so the baseline 3 applies.

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?

A specific verb ("Get") plus a scoped resource ("this site's business overview and public contact details") tells an agent exactly what comes back. It implicitly separates itself from page-level siblings like read_site_page or search_site_pages by promising overview and contact data, but never names an alternative explicitly.

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?

Usage is only implied: the schema note that the site ID comes from find_business hints at the calling sequence, but the description itself gives no when-to-use guidance, no exclusions, and no pointer to get_business_tools or get_locations for related data.

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