Skip to main content
Glama
Sign In

Crs Reports

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Crs Recent

crs_recent
Read-onlyIdempotent

What the Congressional Research Service has published or revised lately — the newest CRS reports and updates, newest first, with their topics and summaries. Answers "what is CRS saying about current legislation right now" and tracks the analysis that follows a bill, a rule or a crisis. Filter by CRS topic or product family.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

NameRequiredDescriptionDefault
daysNoHow far back to look, in days. Default 14, max 365.
limitNoResults to return, 1–50. Default 20.
topicNoA CRS subject term — see crs_topics.
product_classNoCRS product family.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish that this is read-only, idempotent, and non-destructive. The description adds useful behavioral context by specifying newest-first ordering and that results include topics and summaries, which goes beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loaded, with the core purpose stated immediately. The use-case sentence adds value without padding, and the filter sentence is minimal and directly relevant.

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 simple, optional-parameter, read-only listing tool, the description plus fully documented schema and strong annotations is nearly complete. A slightly more explicit statement of the exact output shape would make it fully complete, but this is not a significant gap.

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 100%, so the parameters are already well documented. The description mentions filtering by topic or product family, which reinforces two parameters but adds no meaningful detail beyond the schema.

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

Purpose5/5

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

The description clearly identifies the tool as surfacing recently published or revised CRS publications, newest first, with topics and summaries. It distinguishes itself from siblings like crs_search, crs_report, and crs_topics by focusing on recency and current legislative analysis.

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?

The description gives a strong use context: answering what CRS is saying about current legislation and tracking analysis after a bill, rule, or crisis. It does not explicitly name alternative tools or state when not to use it, but the intended scenario is clear.

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

All Crs Reports toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources