Skip to main content
Glama

sp_read_clause

Read-only

Read a specific numbered clause from a Russian normative document snapshot to retrieve exact text and verify the cited provision.

Instructions

Read a literal numbered HTML clause, e.g. 7.11.1. Repeated occurrences are ambiguous. PDF page blocks may not resolve clause boundaries: use document search and page verification.

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": {
      "snapshot_id": "<snapshot_id>",
      "number": "<number>"
    },
    "name": "sp_read_clause"
  }
}

Input Schema

NameRequiredDescriptionDefault
numberYes
snapshot_idYes
expected_sha256No

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already establish readOnly, non-destructive, closed-world behavior, and the description adds real value on top: it discloses two failure modes (ambiguous repeated occurrences, PDF page blocks failing to resolve boundaries) and a verification procedure. It stops short of describing what is returned or how ambiguity is surfaced to the caller.

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?

Three short, front-loaded sentences with no filler: purpose first, then caveat, then fallback. The telegraphic style slightly hurts readability but nothing is wasted.

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?

With no output schema and zero parameter documentation, the description should compensate more than it does — particularly for expected_sha256 and snapshot_id, and for what a 'clause read' returns. The failure-mode caveats help, but key calling details remain undocumented.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across three parameters, so the description carries the burden — but it only implicitly defines 'number' via the 7.11.1 example. snapshot_id and especially expected_sha256 (an integrity check) are left completely unexplained, leaving an agent to guess their semantics.

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 and resource ('Read a literal numbered HTML clause') with a concrete example number format (7.11.1). It is distinguishable from sp_read_document/sp_search_document by the 'literal numbered' framing, though it never explicitly names what makes it different from reading the whole document.

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?

Gives one concrete routing rule: when PDF page blocks may not resolve clause boundaries, use document search and page verification instead. It also warns that repeated occurrences are ambiguous. However, it never says positively when to prefer this over a plain document read or search, so guidance is partial.

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