Skip to main content
Glama

About Georgia Commons

describe_site
Read-onlyIdempotent

The id grammar, every filter value, and the state's bodies by id. Call it when a search or a fetch needs one you do not have.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "describe_site"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / title
      Removed value: -"describe_siteArguments"
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, closed-world and non-destructive, so the safety profile is covered. The description adds that this is a fallback reference source rather than a primary retrieval path, but says nothing about output size, format, or freshness of the reference data.

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?

Two short sentences with no filler, and the trigger condition is placed where it is easy to find. The first sentence is compressed to the point of ambiguity, which slightly undercuts the brevity.

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?

With zero parameters and no output schema, the description must carry the whole burden of explaining what comes back, and it only sketches this in three noun phrases. An agent knows roughly when to call it but not what shape of data to expect or how large the response is.

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?

The tool takes zero parameters, so the baseline is 4. The description does not need to explain any arguments, and it correctly frames the content (ids, filter values) as reference material rather than inputs.

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 enumerates contents (id grammar, filter values, bodies by id) but never states a verb such as 'returns' — the reader must infer this is a documentation/reference lookup. 'The state's bodies by id' is opaque phrasing that leaves the actual payload unclear.

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

Usage Guidelines4/5

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

'Call it when a search or a fetch needs one you do not have' gives a concrete trigger condition and explicitly situates the tool relative to the search and fetch siblings. It stops short of stating when not to call it, but the invocation context is clear.

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