Skip to main content
Glama

Quiver

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Quiver Congress Trading

quiver_congress_trading
Read-onlyIdempotent

Recent US Congress stock trades — who in Congress bought/sold what, with amount ranges and disclosure dates. Pass a ticker to get the trade history for that company instead ("Congress trades for TSLA"). Example: quiver_congress_trading({ ticker: "NVDA", _apiKey: "your-key" })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tickerNoOptional stock ticker to filter to one company, e.g. "NVDA". Omit for the latest cross-market feed.
_apiKeyYesQuiver Quantitative API key (get one at quiverquant.com; Hobbyist plan from $30/mo)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-quiver-api-key",
+    "ticker": "NVDA"
+  },
+  {
+    "_apiKey": "your-quiver-api-key"
+  }
+]
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false. Description adds behavioral context: 'recent' time frame, amount ranges, and disclosure dates, which supplements 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?

Two sentences plus a clear example. Every part is essential: purpose, usage, and parameter behavior. No redundancy, efficiently front-loaded.

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?

For a tool with only two parameters and no output schema, the description fully covers purpose, usage, parameter semantics, and includes an example. Nothing essential is missing.

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% with descriptions for both parameters. The description adds value by explaining when to use the ticker parameter vs omit, and provides pricing/source info for the API key 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?

Description clearly states the tool returns 'Recent US Congress stock trades' with details on who, what, amount ranges, and disclosure dates. It also differentiates from sibling Quiver tools (contracts, insiders, lobbying) by specifying the domain.

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 clear guidance: pass a ticker for company-specific history or omit for the latest cross-market feed. Includes an example and notes the required API key. Does not explicitly list exclusions but context is sufficient given sibling tool variety.

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

All Quiver 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