Skip to main content
Glama

FinanceQuery

Executive Compensation

get_executive_compensation
Read-onlyIdempotent

Get disclosed executive compensation by year for a symbol.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "get_executive_compensation"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum entries per page; omitted = curated default (25)
cursorNoOpaque continuation token from a previous response's `pageInfo.endCursor`; omitted = first page
fieldsNoComma-separated list of GraphQL field names to include; omitted = curated default
symbolYesStock ticker symbol

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered by structured data. The description adds a small amount of context via 'disclosed' (i.e., proxy-filing compensation) and 'by year', but says nothing about pagination, coverage gaps, or which fiscal fields are returned.

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?

A single well-formed sentence with no filler, and the key resource is front-loaded. It is arguably too terse for a tool with pagination and field-selection parameters, but nothing in it is wasteful.

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

Completeness3/5

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

The tool is a simple read with no output schema and fully documented parameters, so the description is close to sufficient. Still, it leaves out what a returned record contains and how pagination behaves, which the agent must learn from the schema alone.

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 description coverage is 100%, so every parameter (symbol, limit, cursor, fields) is already documented in the schema. The description only reinforces that 'symbol' drives the lookup and that results are yearly; it adds no syntax, format, or default guidance beyond the schema.

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 gives a specific verb ('Get') and a specific resource ('disclosed executive compensation'), plus the scope 'by year for a symbol'. It is clearly distinct in intent from list-style siblings, though it names no alternative and does not clarify how it differs from related financials or holders tools.

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?

There is no explicit when-to-use guidance, no prerequisites, and no mention of alternatives such as financials or key-metrics tools. The only hint is the phrase 'by year', which implies a time-series lookup, but the agent must infer the selection criteria entirely.

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.