Skip to main content
Glama

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

Запис от Основа

get_osnova_entry
Read-onlyIdempotent

One Основа entry by its id (city/kind/slug), with all its facts, sources and check dates.

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

Input Schema

NameRequiredDescriptionDefault
idYese.g. „plovdiv/service/…“, as search_osnova returns it.

Output Schema

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

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.6/5.0
Behavior3/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 that the record is returned in full with facts, sources and check dates, which is useful payload context, but says nothing about lookup failure, staleness, or missing-entry behavior.

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?

A single tight sentence with zero filler, front-loading the cardinality ('One') and the identifier format before the return contents.

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 one-parameter, read-only, idempotent fetch with a full output schema, the description covers identity, input shape and payload scope. Return values needn't be explained because an output schema exists; only error/not-found handling is left unaddressed.

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 example already shows the composite path form 'plovdiv/service/…'. The description only restates the components (city/kind/slug), adding no format, encoding, or case-sensitivity detail beyond the 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?

States a specific retrieval action on a named resource ('One Основа entry') and pins down the identifier ('by its id (city/kind/slug)'), plus what comes back (facts, sources, check dates). It is clearly a by-id fetch rather than a search, though it never names search_osnova in the description itself to make the split explicit.

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: you call this when you already hold an entry id, and the schema note ('as search_osnova returns it') hints the id comes from the search tool. There is no explicit when-to-use/when-not or statement of what to do if the id is unknown or stale.

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