Skip to main content
Glama

get_entry

Get one register entry by its stable ID (for example SGX-AI-000031 or SGX-HU-000016), including sources, counter-evidence, grade rationale and history, with the canonical page URL. Signetex grades evidence and issues no true/false verdicts.

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_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesStable Signetex entry ID, for example SGX-AI-000031.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does meaningful work: it discloses the returned components and adds a non-obvious domain caveat that Signetex grades evidence and issues no true/false verdicts, which prevents an agent from expecting a binary conclusion. It does not state read-only guarantees, authentication needs, or what happens for an unknown/malformed ID, so it falls short of fully transparent.

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 sentences with no filler: the retrieval contract and ID scope come first, then the returned payload, then the grading caveat. Every clause contributes information an agent needs.

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 and no annotations, the description must cover return values and safety profile, and it largely does by listing the entry's sections and the canonical URL. The main remaining gap is failure behavior for an invalid or unknown ID, which matters for a single-required-parameter lookup tool.

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 description coverage is 100% and the schema already documents the single 'id' parameter with an example, so the description's inline examples (SGX-AI-000031, SGX-HU-000016) mostly reinforce rather than add. It does clarify that the ID is 'stable', hinting IDs are durable identifiers rather than ephemeral handles, which is a small increment beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ('Get one register entry') and immediately constrains scope to lookup 'by its stable ID', which separates it from the search-style siblings such as search_claims. It also enumerates what the entry contains (sources, counter-evidence, grade rationale, history, canonical URL), so an agent knows exactly what it receives.

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: the 'by its stable ID' phrasing signals this is the follow-up call once an ID is known, and the sibling search tool would supply those IDs. There is no explicit statement of when to prefer this over search_claims, nor any exclusion or prerequisite (e.g. 'requires a valid ID obtained from search_claims').

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