Skip to main content
Glama

Veyrul media knowledge hub

Fetch a record

get_record
Read-only

Fetch an authorized record by ID under the server protocol boundary. Guide catalog2.0 requires a current agent credential and current complete editorial keep review; legacy guide reads are unavailable. markdown (default): compact, with reusable resource locations, up to 5 replies (accepted first) or a project's tasks. json: full envelope incl. etag (HTTP PATCH and record review send it as Hub-If-Match), evidence, rights; body follows its type's schema, ignore unknown keys. execution=independently_reproduced reflects current eligibility only (an unchanged, public, independent reproduction), not history.

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

Input Schema

NameRequiredDescriptionDefault
idYesPermanent public record ID returned by a Veyrul search or listing.
formatNomarkdown is the concise readable default; json returns the full structured record.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / format / description
      Added value: +"markdown is the concise readable default; json returns the full structured record."
    • addedInput schema / properties / id / description
      Added value: +"Permanent public record ID returned by a Veyrul search or listing."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations, the description discloses authorization requirements, format-dependent return behavior, etag handling, and the meaning of independently_reproduced status. It does not cover error or not-found behavior, but adds substantial behavioral context.

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?

The description is a dense run-on paragraph with jargon such as 'server protocol boundary' and 'editorial keep review'. It contains useful information but is not front-loaded or cleanly structured for quick scanning.

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?

For a two-parameter read tool without an output schema, the description covers authorization, return formats, etag usage, and status semantics. It could say more about error behavior, but the main call-relevant context is present.

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 schema already documents both parameters at 100% coverage, but the description adds meaningful detail about the format enum, including what markdown and json return and how the json body relates to its type schema.

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 states a specific verb and resource: fetch an authorized record by ID. It does not explicitly differentiate this from sibling tools such as get_record variants or listing tools, but the core purpose is clear.

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: use this when you need an authorized record by ID. The description adds credential and editorial-review prerequisites, but it does not state when to choose this over alternatives or when not to use it.

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