Skip to main content
Glama
TurkActuary MCP

TurkActuary MCP

by afsharid

belge_getir

Read-onlyIdempotent

Retrieves the complete text for a document chunk using its identifier, such as a consolidated regulation section or risk pool entry, supporting insurance regulation and actuarial reference tasks.

Instructions

Parça kimliğiyle (ör. mevzuat-5684_consolidated:3 ya da edu_risk_pool) tam metni getirir.

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": {
      "kimlik": "<kimlik>"
    },
    "name": "belge_getir"
  }
}

Input Schema

NameRequiredDescriptionDefault
kimlikYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/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 profile is covered. The description adds one genuinely new behavioral fact — that the response is the full document text rather than metadata — but says nothing about what happens with an unknown ID, chunk granularity, or response size.

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?

One sentence, front-loaded with the retrieval key and followed by concrete examples; every clause earns its place and nothing is padded.

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 single-parameter read-only retriever with full annotation coverage and no output schema, the description supplies enough to call it correctly. The only real gap is the absence of an explicit pointer to the search sibling for obtaining IDs.

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?

Schema description coverage is 0%, so the description must carry the parameter, and it does: it names the parameter's meaning as a document identity and supplies two illustrative values, including the 'prefix:index' chunk form. It stops short of explaining the ID syntax rules, but the examples convey the pattern.

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 ('tam metni getirir' — fetch the full text) qualified by the retrieval key ('Parça kimliğiyle'), and gives two concrete ID examples. It is clear what the tool does, though it never names 'mevzuat_ara' as the lookup-by-query alternative, so the boundary with that sibling must be inferred.

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 presence of an identity parameter suggests calling this once an ID is known from a search result, but the description never states that condition or excludes calling it with free-text queries. No prerequisites or failure guidance are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.