Skip to main content
Glama

sp_sources

Read-only

Lists implemented sources, coverage limits, local index counts, and planned adapters for Russian normative documents such as SP and GOST, so you can verify which references the server can check.

Instructions

Implemented sources, coverage limits, local index counts and planned adapters.

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_sources"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered. The description adds that the response concerns implemented sources, coverage limits, index counts and planned adapters, which hints at returned content. It does not describe output shape, freshness, or why 'planned adapters' would be included in a live tool response.

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?

It is a single short fragment with no wasted clauses, but it is a noun phrase lacking a leading verb or subject, which hurts front-loading. Structure is weak even if length is appropriate.

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 zero-parameter, read-only tool with no output schema, the description should say what the agent gets back and how to use it. It lists content categories but omits the return form and any interpretation guidance, leaving a moderate gap.

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?

The tool takes zero parameters and the schema is an empty object, so there is nothing for the description to disambiguate. Baseline for a parameterless tool applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The phrase names the subject matter (implemented sources, coverage limits, local index counts, planned adapters) but supplies no verb, so an agent must infer that it retrieves a status/coverage report. It is more informative than a restatement of the name 'sp_sources', but it does not clearly distinguish the tool from siblings such as sp_browse_catalog or sp_check_status.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of alternatives such as sp_browse_catalog or sp_check_status, and no stated preconditions. The agent must guess whether this is a diagnostic call, a capability listing, or a prerequisite step.

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