Skip to main content
Glama

Нишка – отворен слой

Документ от Извор

get_izvor_document
Read-onlyIdempotent

One Извор record by id, with its full stored excerpt and when Nishka first and last saw it.

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

Input Schema

NameRequiredDescriptionDefault
idYese.g. „dv:…“, as search_izvor returns it.

Output Schema

NameRequiredDescriptionDefault
documentYes
citationsYesEvery source the result rests on. Cite url; give checkedOn or publishedOn.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / citations / items / properties / licence / enum
      Previous value: -[
      -  "CC-BY-4.0",
      -  "official-record"
      -]New value: +[
      +  "CC-BY-4.0",
      +  "official-record",
      +  "ODbL-1.0"
      +]
  2. 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, closed-world behavior, so the safety profile is covered. The description adds genuine context beyond that by stating the returned excerpt is the 'full stored' one (i.e. untruncated, potentially large) and that the record carries first/last observation timestamps. It does not say what happens when the id does not exist.

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?

One tightly constructed sentence that front-loads the core result and appends the two payload details; nothing is wasted. The only friction is the unexplained proper noun 'Nishka', which an agent may not be able to interpret.

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 an output schema present, the description needn't document return structure, and rich annotations cover safety semantics. For a one-parameter lookup this is nearly complete; only miss/error behavior for an unknown id is left unstated.

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?

There is a single required parameter with 100% schema description coverage, which already documents the expected id form with an example. The description adds no further meaning about the id beyond what the schema provides, so the baseline 3 applies.

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 names a specific verb and resource: fetch one Извор record by id, plus what comes back (full stored excerpt, first/last-seen timestamps). It implicitly distinguishes itself from the batch search sibling by being the singular-by-id lookup, though it never names search_izvor as the alternative.

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 id format hint in the schema ('as search_izvor returns it') suggests the follow-up-after-search workflow, but the description itself contains no explicit when-to-use or when-not-to-use guidance.

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