Skip to main content
Glama

Kiltikonet (public)

Observatory — dossier de recherche vérifiable

observatory_research_packet
Read-onlyIdempotent

Faits autorisés de l'Observatory avec périodes et date source, sans provenance fournisseur.

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": {
      "territory": "<territory>"
    },
    "name": "observatory_research_packet"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
indicatorNo
territoryYes

Output Schema

NameRequiredDescriptionDefault
factsNo
indicatorNo
territoryYes
fact_countYes
limitationsNo
completenessNounknown
retrieved_atYes
source_routeYes
provenance_statusNoprovider_details_withheld
source_generated_atNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds one piece of genuine behavioral context beyond that: results carry source dates and deliberately omit supplier provenance, and 'autorisés' implies a curation/licensing filter. It still says nothing about result size, coverage, or what happens when territory/indicator yield no matches.

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?

It is a single compact clause with no filler, so nothing is wasted. However, the brevity comes at the cost of specification rather than being earned conciseness — the sentence is front-loaded with a vague qualifier ('Faits autorisés') instead of the action.

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?

An output schema exists, so return values need not be described, but the tool is still underspecified: no verb, no usage guidance among many overlapping siblings, and zero explanation of a required 'territory' parameter or the 'indicator' filter. For a filtering research-endpoint with three inputs, this leaves an agent guessing how to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across three parameters, and the description mentions none of them: 'territory' (required), 'indicator' (optional, nullable) and 'limit' (default 25) are all left unexplained. The one hint, 'périodes', relates to output rather than any input, so the description does not compensate for the total schema gap.

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 the resource ('Faits autorisés de l'Observatory') and characterizes the payload ('avec périodes et date source, sans provenance fournisseur'), which hints at a curated fact-retrieval tool. But it states no verb and never distinguishes itself from close siblings such as observatory_global_facts or observatory_caribbean_brief, so an agent cannot tell which one to pick from purpose alone.

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 when-to-use instruction, no exclusions, and no mention of the sibling tools that clearly overlap (observatory_global_facts, observatory_caribbean_brief, observatory_regional_lenses). The only implicit cue is 'Faits autorisés', which might suggest licensed/approved data, but that is not framed as a selection criterion.

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