Skip to main content
Glama

corporate_lobbying_by_ticker

Access normalized corporate lobbying filings by ticker, including income, expenses, issue codes, and government entities, with date filtering and JSON or CSV output.

Instructions

Normalized corporate lobbying filings: { format: "json", ticker, name, series: [{date, filing_uuid, filing_year, quarter, client_name, registrant_name, income, expenses, issue_codes, government_entities}, ...], series_count, series_total } CSV returns the sliced series.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reqYes
Behavior2/5

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

No annotations provided. Description mentions format and limit but does not disclose pagination, data availability constraints (e.g., US only), or effects of date parameters. Lacks behavioral details beyond output structure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Very concise (one sentence + JSON-like block), but the structure mixes code and prose, making it slightly messy. Could be more readable.

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

Completeness2/5

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

No output schema, so description must fully document return values. It shows fields but lacks clarity on input parameters and data semantics. Incomplete for a tool with nested objects and multiple filters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description should explain parameters. It only shows the output structure, not the meaning of ticker, date_from, date_to, limit, or format. Almost no added semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Normalized corporate lobbying filings:' and shows a structure with ticker, name, and series, which implies it returns lobbying data for a given ticker. It is fairly clear but could be more explicit about 'get' or 'retrieve'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternative ticker-based tools (e.g., analyst_ratings_by_ticker, news_by_ticker). No mention of context or prerequisites.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ahmetsbilgin/finbrain-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server