Skip to main content
Glama
cm2489

oravan

by cm2489
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Look up representatives by ZIP

lookup_representatives
Read-only

Find your U.S. House member and two Senators by ZIP code: get names, party, phone, website, and the district office numbers to call. Multi-district ZIPs include a link to refine by address.

Instructions

Look up a person's U.S. House member and two Senators by 5-digit ZIP code. Returns each member's name, party, phone, official website, portrait URL, and district office phone numbers - the number a constituent should actually call. Some ZIP codes span more than one congressional district (needs_address: true, all candidate districts returned); this tool does not perform address-level refinement itself in this release - point the person to the response's reps_url, where a stateless, unlogged Census-geocoder proxy narrows it to a single district from a street address that Oravan never stores. When a House seat currently has no member, vacancies lists the empty seat(s) (state + district) explicitly - the departed member is never returned as if still serving, and no election timeline is implied.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zipYes5-digit U.S. ZIP code.
localeNoResponse language: "en" (default) or "es".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Exceeds annotations by explaining return fields, multi-district handling, vacancy behavior, and the stateless proxy. No contradiction with readOnlyHint and openWorldHint.

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?

Well-structured: first sentence states main purpose, then details returns, then edge cases. Slightly verbose but each sentence adds necessary information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers all relevant aspects: return data fields, edge cases (multi-district, vacancies), and behavior (no address storage). No output schema, but description compensates adequately.

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?

Schema coverage is 100%, and the description adds context: ZIP pattern, language enum, multi-district edge case. Adds value beyond the schema with practical usage details.

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?

Clearly states it looks up U.S. House member and two Senators by 5-digit ZIP code. Differentiates from siblings like get_representative by specifying the lookup method and scope.

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?

Provides guidance on when to use (by ZIP), explains limitations for multi-district ZIPs, and directs users to reps_url for address refinement. Could explicitly contrast with alternatives but is adequate.

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