Skip to main content
Glama

sp_browse_catalog

Read-only

Browse paginated catalogs of Russian normative documents (SP and GOST) from meganorm or rosstandard. Retrieve exact URLs and discovery checksums for each catalog page.

Instructions

Discover one page of meganorm (sp|gost|gost_r|snip) or rosstandard (sp|gost). Page is zero-based. Returns exact URLs and discovery checksums. Discovery is not a status check.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sp_browse_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
sourceNomeganorm
catalogNosp
refreshNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly/openWorld/non-destructive, lowering the bar. The description adds that results include exact URLs and discovery checksums and clarifies the page is zero-based, but says nothing about pagination termination, rate limits, or what a 'checksum' is for.

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?

Four short sentences, no filler, with the subject and page semantics front-loaded. The parenthetical value lists are terse to the point of being cryptic but not wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 4-parameter tool with 0% schema coverage and no output schema, the definition covers entity and paging semantics but omits the meaning of 'refresh' and any indication of how to detect the last page or what the response items look like. Adequate but with clear holes.

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?

With 0% schema coverage the description must carry parameter meaning, and it does substantial work: it explains 'page' is zero-based and maps catalog values to sources (meganorm supports sp|gost|gost_r|snip; rosstandard supports sp|gost). The 'refresh' parameter is left entirely unexplained, which is the main gap.

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 verb ('Discover') and resource ('one page of meganorm ... or rosstandard'), and even enumerates the catalog/source value sets. It is clearly a catalog-listing tool, though 'Discover' remains slightly abstract (list documents? enumerate sections?) and the title is absent.

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 closing sentence 'Discovery is not a status check' usefully steers the agent away from status-checking siblings. However, no positive when-to-use statement or named alternative (e.g. search vs. browse) is given, so routing is implied rather than explicit.

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