Skip to main content
Glama

Kiltikonet (public)

Observatory — brief Caraïbe

observatory_caribbean_brief
Read-onlyIdempotent

Dossier consolidé en lecture seule : indicateurs culturels, couverture territoriale, corpus de référence, lentilles régionales et vue Caraïbe. Les sections conservent les réponses de leurs routes sources ; generated_at indique l'heure de compilation, pas la date de mise à jour des données sources.

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Output Schema

NameRequiredDescriptionDefault
scopeYes
sourcesYes
read_onlyYes
disclaimerYes
provenanceYes
generated_atYesHeure de compilation, pas fraîcheur des données.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuine unannotated context: each section preserves the raw response of its source route, and generated_at is compilation time, not source-data freshness — a real trap for an agent reporting data recency. It omits cost/latency expectations for an aggregate call, which is the remaining gap.

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?

Front-loaded with the key fact ('lecture seule', consolidated dossier), followed by the section inventory and then the generated_at caveat. Three dense statements, no filler. The section list is slightly run-on but each item tells the agent something it will receive.

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?

An output schema exists, so return values need not be described. But for a one-parameter aggregate over five source routes, the description leaves open what `limit` scopes, whether sections are independently truncated, and roughly how large/expensive the response is. Adequate but with clear gaps for a composite tool.

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% and the single `limit` parameter (integer, default 50) is never mentioned in the description. It is unclear whether `limit` caps records per section or across the whole dossier, which materially changes what an agent should pass. The description does nothing to compensate for the undocumented parameter.

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 gives a specific noun phrase ('Dossier consolidé en lecture seule') and then enumerates the five sections it bundles — cultural indicators, territorial coverage, reference corpus, regional lenses and Caribbean view — which maps closely onto the sibling tools (observatory_global_corpora, observatory_global_territories, observatory_regional_lenses, observatory_caribbean_overview). That enumeration effectively signals this is the aggregate over those siblings. It stops short of naming them as alternatives, so an agent must infer the aggregation relationship rather than read it.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: 'consolidé' suggests this is the one-shot snapshot to use when the whole picture is wanted, but there is no explicit 'use this instead of calling the four section routes separately' or any precondition. No exclusion or guidance on when a narrower sibling is preferable.

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