Skip to main content
Glama

sp_search_documents

Read-only

Search Russian SP and GOST normative documents by designation or keywords to return candidate matches for status and applicability checks.

Instructions

Search by full designation or words. Returns candidates, never confirmed applicability. Online search queries Rosstandard and Gostinfo metadata, the FCS SP registry and bounded MegaNorm catalogues. Default concept mode uses Russian morphology, BM25, spelling corrections and a curated lexicon, no model. Optional hybrid/semantic modes require a separately configured local embedding index; no generation API. Explicitly inactive documents are hidden by default; include_inactive restores historical results. Unknown or conflicting status remains visible and is never labelled active. Page is a slice of the merged result, independent of bounded catalogue discovery. Inspect source_errors and search coverage.

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": {
      "query": "<query>"
    },
    "name": "sp_search_documents"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoconcept
pageNo
limitNo
queryYes
onlineNo
refreshNo
include_inactiveNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.5
    • addedInput schema / properties / include_inactive
      Added value: +{
      +  "default": false,
      +  "title": "Include Inactive",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / mode
      Added value: +{
      +  "default": "concept",
      +  "title": "Mode",
      +  "type": "string"
      +}
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, openWorld, non-destructive), and the description adds substantial context on top: no model or generation API by default, hybrid/semantic modes needing a separately configured local embedding index, inactive documents hidden unless include_inactive, and unknown/conflicting status never labelled active. It also flags source_errors and coverage for verification. It stops short of describing result freshness or what refresh actually re-queries.

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 critical constraint (candidates, not confirmed applicability) is correctly front-loaded and the mode/behaviour sentences are informative. But several lines are telegraphic fragments ("Page is a slice of the merged result, independent of bounded catalogue discovery."), and registry names like Rosstandard, Gostinfo and MegaNorm add length without helping tool selection.

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 7-parameter, open-world search with no output schema and no schema descriptions, the definition covers the important behavioural surprises: default no-model concept mode, embedding-index prerequisite for hybrid, hidden inactive documents, and source_errors. The gaps are the undocumented limit/refresh semantics and the absence of any indication of what a candidate record contains.

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 0% across 7 parameters, so the description must carry the load. It explains mode (concept default vs optional hybrid/semantic, with the local index prerequisite), online (which registries are queried), include_inactive, and page as a slice of the merged result. It says nothing about limit, refresh, or the query format (“full designation or words” is the only hint), leaving three parameters undocumented in both places.

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?

"Search by full designation or words. Returns candidates, never confirmed applicability" gives a specific verb and resource plus an explicit scope limit on what the results mean. It clearly separates a discovery search from a confirmation/status tool, though it never names the singular sibling sp_search_document or sp_search_status.

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?

The line "Returns candidates, never confirmed applicability" implies this is a discovery step whose hits still need verification elsewhere, and the mode/online/inactive explanations imply when each switch applies. However, no alternative tool is named and there is no explicit "use this instead of X when..." routing, so the agent must infer the workflow.

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