Skip to main content
Glama

Get one registry entry

get_announcement
Read-onlyIdempotent

Get one entry of the DiscoverIA registry by id: claim, claimant, current status with its rule, dated status history with sources, verifiers, links, statement fidelity, events, related frontiers and the plain-language summary. A status says where the evaluation stands, not whether the result is true.

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": {
      "id": "<id>"
    },
    "name": "get_announcement"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesEntry id (slug), e.g. 'gauss-sphere-packing-dim8', as returned by search_announcements.
langNoLanguage of titles, labels and texts: 'fr' (French) or 'en' (English). Default 'en'. Use the user's language.en

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety bar is low. The description still adds real value by disclosing the shape of the returned record and one important interpretive caveat: 'A status says where the evaluation stands, not whether the result is true.' It does not cover behavior on an unknown id.

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?

Two sentences, front-loaded with the verb and resource, then the field inventory and the status caveat. The long comma-separated field list is dense but each item is a genuine payload component, so there is little waste.

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?

With no output schema, the description correctly takes on the burden of describing what comes back, enumerating the record's sections and adding a semantic caution about status. It falls short only on error/not-found behavior and the effect of the lang parameter.

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

Parameters3/5

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

Schema coverage is 100%, so both the slug id and the 'fr'/'en' lang enum are fully documented in the schema. The description only echoes 'by id' and never mentions the lang parameter or how language choice affects returned titles and summaries, so it adds nothing beyond the schema baseline.

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?

States a specific verb and resource ('Get one entry of the DiscoverIA registry by id') and enumerates the payload: claim, claimant, status, history, verifiers, links, fidelity, events, frontiers, summary. That is far more than a restatement of the title, though it never names sibling tools like get_citation or get_frontier to draw the boundary explicitly.

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 only implied: fetch a single entry by id, which presupposes an id obtained elsewhere (the schema, not the description, points at search_announcements). There is no statement of when to prefer this over search_announcements or the other get_* siblings, and no exclusions.

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