Skip to main content
Glama

overview

Inspect all sites in the store with their contexts, relations, contested claims, finds, and open issues to understand the full excavation record.

Instructions

Every site in the store: contexts, relations, contested claims, finds, open issues.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses that the tool returns a comprehensive view including contested claims and open issues, which is useful behavioral context. However, it does not mention whether the operation is read-only, how expensive it might be, or any other operational traits beyond the content scope.

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?

The description is a single, front-loaded sentence fragment that efficiently lists the included data types. It is concise and wastes no words, though it could be slightly more structured with a clear verb.

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?

Given the tool's simplicity (zero parameters, output schema present), the description covers what data is returned. However, it omits usage guidance and does not clarify how it differs from siblings like 'store_info' or 'query', leaving a gap in decision-making context.

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 has zero parameters, so the baseline score is 4. The description does not need to explain parameter semantics, and the schema is empty.

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 lists the contents of an overview ('contexts, relations, contested claims, finds, open issues') and implies comprehensiveness ('Every site in the store'), but it lacks a clear verb and does not explicitly state what the tool does (e.g., list, summarize, aggregate). It distinguishes itself from narrower siblings like 'issues' by covering all sites, but the purpose remains somewhat vague.

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 alternatives such as 'store_info', 'query', or 'issues'. The description provides no context about appropriate scenarios, exclusions, or prerequisites, leaving the agent to infer usage from the name alone.

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