Skip to main content
Glama

describe

Retrieve a stratigraphic unit's record, matrix depth, adjacent units, same-as links, contested claims, finds, and open issues in one query.

Instructions

One unit: its record, matrix depth, what lies directly above/below, same-as units, contested claims, finds and open issues.

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": {
      "unit": "<unit>"
    },
    "name": "describe"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNo
unitYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It lists some returned content (record, matrix depth, above/below, same-as units, contested claims, finds, open issues) but does not state that the operation is read-only, what permissions are required, or how errors are handled.

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 definition is short, but it is a noun-phrase fragment rather than a clear sentence with a verb. The content is front-loaded as a list of outputs, which is concise but not optimally structured for quick comprehension.

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?

For a two-parameter detail tool with an output schema, the description should at least clarify purpose, usage context, and the optional 'site' parameter. It omits usage guidance and parameter semantics, leaving key gaps despite its brevity.

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 description coverage is 0%, so the description must explain both parameters. It implies the 'unit' parameter by saying 'One unit' but never mentions the optional 'site' parameter or how it scopes the result.

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 resource ('One unit') and enumerates what the response includes, but it never states a verb or explicitly says this retrieves a unit description. An agent can infer it is a detail view, but the purpose remains vague and fragmentary.

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 guidance on when to use this tool versus siblings like 'above', 'below', 'overview', or 'query'. The description provides no context, exclusions, or alternatives.

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