Skip to main content
Glama

graph_overview

Retrieve record counts, date range, and valid dimension values for a livestock-health RDF graph to scope queries and validate filters.

Instructions

What the graph contains: number of records, date range, and the valid values of every dimension (species, pathogen, country, lab, breed, sample_type, diagnostic_test, production_stage).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry behavioral disclosure. It explains the returned data (counts, dates, dimension values) but says nothing about read-only status, permissions, cost, or output format beyond the field list.

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 front-loaded sentence states the tool's output scope and uses a parenthetical dimension list that is informative rather than filler. It is appropriately sized for a zero-parameter overview tool.

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 zero-parameter overview tool with no output schema, the description supplies the key return contents but lacks guidance on when to consult it and does not note read-only behavior. It is adequate but incomplete for an agent choosing among metadata-style tools.

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 there is no parameter semantics for the description to add. Baseline 4 applies because schema coverage is moot with an empty parameter list.

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 names the resource (the graph) and enumerates the overview contents: record count, date range, and valid values across dimensions. It is clear what the tool returns, though it does not explicitly contrast itself with other lookup-style tools.

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 explicit when-to-use or when-not-to-use guidance; the description only states what content is available. An agent can infer it is an overview tool, but no conditions or alternatives are provided.

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