Skip to main content
Glama
cm2489

oravan

by cm2489
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

What's moving in Congress

whats_moving
Read-only

Find urgent U.S. Congress bills from the last week, with plain-language summaries and optional topic filter. Returns an honest empty list when quiet, flags stale data.

Instructions

What's moving in Congress recently: active, plain-language-decoded bills that cleared Oravan's 'act now' urgency bar within the last N days (default 7), optionally filtered by topic. Returns an honest empty list with quiet_week: true when nothing has cleared the bar - this tool never pads the list to look busier than Congress actually is this week. If the list is empty because Oravan's own data sync looks stale rather than Congress being quiet, data_stale is set instead so that distinction is never lost.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoLookback window in days (default 7).
limitNoMax results (default 10, max 50).
topicNoOne of the 12 issue categories.
localeNoResponse language: "en" (default) or "es".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses honest empty list behavior with quiet_week/data_stale flags, never pads results, and mentions Oravan's urgency bar and plain-language decoding.

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?

Description is one paragraph, front-loaded with purpose, and each sentence adds value. Slightly lengthy but efficient.

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?

With no output schema, the description explains return value shape (honest empty list with flags) and key behavior. Could clarify bill fields, but adequate.

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 has 100% parameter description coverage. The description adds default values (days=7) and mentions topic filtering but does not provide additional syntax or meaning 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 states the tool returns active bills that cleared an urgency bar, optionally filtered by topic. It distinguishes from siblings like get_bill (single bill) and search_bills (general search) by focusing on recent urgent bills.

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 implies use for recent urgent bills and explains empty result behavior. It does not explicitly name alternatives or state when not to use, but context is clear.

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

Deploy Server

Other Tools