Skip to main content
Glama

Legislative pipeline

lexatlas_pipeline
Read-onlyIdempotent

Bills and laws by legislative stage (introduced, readings, signed, published, in force) across CIS jurisdictions. Call it for questions about pending legislation. Optional jur (csv), stage (csv), since (YYYY-MM-DD), linked_only, limit.

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": "lexatlas_pipeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
jurNocomma-separated jurisdiction codes, e.g. ru,kz
limitNo
sinceNo
stageNo
linked_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds the stage taxonomy and jurisdiction coverage, but says nothing about ordering, default limit, or what a result row looks like.

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?

Two sentences, front-loaded with purpose and scope, followed by a compact parameter note. The trailing 'Optional ... limit' fragment is telegraphic but efficient; nothing is padded.

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 five-parameter, zero-required list tool with no output schema, an agent still lacks the meaning of linked_only, the behavior of limit, and any hint of return shape or ordering. The stage and date-format detail is helpful, but key gaps remain.

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 coverage is only 20%, so the description carries real weight here: it gives the CSV convention for jur and stage, the YYYY-MM-DD format for since, and stage vocabulary from the first sentence. However, linked_only is named with no meaning at all, and limit has no default or maximum, so the low-coverage gap is only partly closed.

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 resource (bills and laws), a specific dimension (legislative stage), and a scope (CIS jurisdictions), with the stage values enumerated. It is clear what the tool returns, though it doesn't explicitly contrast with lexatlas_search or lexatlas_get.

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

Usage Guidelines4/5

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

"Call it for questions about pending legislation" gives a clear selection signal for this tool. There are no exclusions or named alternatives, so it stops short of the top score.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.