Skip to main content
Glama
Sign In

Committee Releases

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Committee Document

get_committee_document
Read-onlyIdempotent

Read a committee document page: its headline, publication date, the text the committee published, and the attached documents (usually PDFs — letters, transcripts, reports) with URLs and sizes. Pass a url from search_committee_documents. Note that PDF text is NOT extracted — attachments are returned as links, so quote the page text and cite the attachment URL rather than claiming to have read the PDF.

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": {
      "url": "https://oversight.house.gov/release/chairman-comer-issues-two-subpoenas-to-leon-black/"
    },
    "name": "get_committee_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesFull committee document URL, as returned by search_committee_documents

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

While annotations already indicate read-only, idempotent, non-destructive behavior, the description adds crucial limitations: PDF text is NOT extracted, attachments are returned as links with URLs and sizes. This tells the agent exactly what it can and cannot do with the returned data, going 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 three concise sentences, with the primary function front-loaded in the first sentence. Every sentence carries useful information: what it reads, how to pass the URL, and the PDF caveat.

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?

Given there is no output schema, the description explicitly enumerates the return fields (headline, publication date, text, attachments with URLs and sizes) and the PDF limitation. With only one parameter and a clear usage flow, the description provides sufficient context to use the tool correctly.

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?

The schema's single parameter 'url' already has a thorough description ('Full committee document URL, as returned by search_committee_documents'), and the tool description repeats this guidance. Since coverage is 100%, the description adds little new semantic value for the parameter.

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 uses a specific verb ('Read') and names the exact resource ('committee document page'), listing the fields it returns (headline, publication date, text, attachments). This clearly differentiates it from search_committee_documents and other sibling tools.

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 instruction 'Pass a url from search_committee_documents' clearly states when to use this tool – after obtaining a URL via search. It also provides an important usage caveat: PDF text is not extracted, so the agent should quote page text and cite attachment URLs rather than claim to have read PDFs. However, it does not explicitly name alternative tools or exclusionary conditions.

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

All Committee Releases 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