Agent interaction server — Kazakhstan

Suggest a missing term

suggest_term

Idempotent

Suggest a category or facet term missing from the taxonomy (e.g. a new equipment model). Use only after resolve_terms returned not_found; meanwhile use a tag. Suggestions are moderated.

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": {
      "kind": "<kind>",
      "label": "<label>"
    },
    "name": "suggest_term"
  }
}

Input Schema

Name	Required	Description
`kind`	Yes
`facet`	No	For kind=facet.
`label`	Yes
`parent`	No	Closest existing category.
`synonyms`	No
`client_request_id`	No	Idempotency key: repeating a call with the same key returns the original result. New key per intended action.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Beyond the annotations' non-read-only, non-destructive, and idempotent profile, the description discloses that suggestions are moderated, implying review rather than immediate taxonomy insertion. It could further clarify the resulting lifecycle, such as whether the response is only a pending suggestion and when an approved term becomes usable.

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?

Three compact sentences front-load the purpose, then provide the selection rule and finally the moderation behavior. Every clause adds actionable information without repeating schema constraints or annotations.

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?

The description, schema, and annotations together support correct selection and basic invocation, including prerequisites, idempotency, and the main parameter relationships. Because there is no output schema, the lack of any explanation of the returned suggestion status or post-submission outcome leaves a modest completeness gap.

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?

The description reinforces the meaning of kind through the category/facet distinction and illustrates a possible label with the equipment-model example. With 50% schema coverage, it does not fully compensate for undocumented semantics, particularly when to supply synonyms or how to choose optional enrichment fields.

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 uses a specific verb and resource: suggesting a missing category or facet term in the taxonomy, with a concrete equipment-model example. Its reference to resolve_terms also distinguishes this submission workflow from term resolution.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit prerequisite: use the tool only after resolve_terms returns not_found. It also supplies interim guidance to use a tag, clearly covering both when to invoke the tool and what to do beforehand.

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

All Agent interaction server — Kazakhstan tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?