Skip to main content
Glama

Lobbying by listed US companies (Lobbying Disclosure Act)

get_company_lobbying
Read-onlyIdempotent

What a listed US company spent on federal lobbying, per quarter, from the Lobbying Disclosure Act reports (lda.gov): its own in-house expenses and the income outside lobbying firms reported from it, kept apart, plus its most recent reports with links. Give ticker or company. Without either, a ranking of the listed companies with the largest own lobbying expenses over the last four quarters.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
limitNoWithout a company: how many companies to rank. Default 20.
tickerNoThe company's ticker, e.g. NVDA.
companyNoPart of the company name, e.g. Nvidia. Use ticker when you know it.
filingsNoHow many recent reports to list. Default 10.
quartersNoHow many quarters, newest first. Default 8.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world semantics, so the description only needs supplementary context. It adds the data source (lda.gov), the fact that in-house and outside-firm figures are reported separately, and that reports come with links — useful framing for interpreting results.

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?

Two sentences, the first front-loading what the tool returns and the second stating the input modes. The first sentence is dense and slightly run-on ('the income outside lobbying firms reported from it, kept apart'), but nearly every clause carries meaning.

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?

There is no output schema, so the description must convey the shape of results; it does so at a high level (in-house vs. outside-firm income, recent reports with links). Default parameters and units are left to the schema, which is acceptable given full coverage there.

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 coverage is 100% and each parameter is already documented, so the baseline is 3. The description clarifies the no-company ranking mode and the metric used (largest own lobbying expenses over the last four quarters), which lightly reinforces `limit` and `quarters` but adds no new syntax or constraints.

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?

States a specific resource (quarterly federal lobbying spend of a listed US company), the source (LDA reports at lda.gov), and the exact figures returned: in-house expenses and outside-firm income kept separate, plus recent filings with links. An agent can tell immediately this is lobbying disclosure data, not insider or holdings data.

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?

Explicitly describes the two invocation modes: pass a ticker or company name for that issuer, or omit both to get a ranking of top spenders. It does not name alternative tools or state when to prefer a sibling (e.g., politician trades), so it stops short of full routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources