Skip to main content
Glama

overview

Read table definitions, data cleaning steps, and caveats before analyzing. Call this first to understand the fictional hospital dataset and avoid misinterpreting results.

Instructions

What the tables are, how the data was cleaned and the caveats to respect before analysing. Read this first.

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.1.2

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden and does disclose the substantive traits: it is a read-only orientation payload whose content includes cleaning provenance and caveats that constrain later analysis. It does not say whether the content is static or dataset-specific, or how large the payload is, which is the remaining gap for a zero-parameter tool.

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

Conciseness5/5

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

Two short sentences with no filler, and the highest-value instruction ('Read this first') is placed last as a punchy call to action while the content scope is front-loaded. Every clause earns its place.

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

Completeness4/5

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

An output schema exists, so the description need not explain return values, and for a no-parameter orientation tool the stated scope plus the read-first directive is close to sufficient. It could still say whether the overview is global or dataset-scoped, which matters given siblings that operate on specific tables.

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 and there is no parameter meaning for the description to add. Nothing in the text conflicts with the empty schema.

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?

The description states the resource content concretely: table inventory, how the data was cleaned, and caveats to respect before analysing. That distinguishes it from list_tables (enumeration), describe_table (single-table schema) and data_quality_log (quality events), though it never names those siblings explicitly. The verb is implicit ('what the tables are' rather than 'returns documentation about'), which keeps it just short of a 5.

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?

'Read this first' gives an explicit ordering instruction and the phrase 'caveats to respect before analysing' makes the trigger condition clear. It does not state any when-not condition or point to a sibling for a narrower need, so it stops at clear context rather than full routing guidance.

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