signals

exec_moves

Read-only

List executive appointment, promotion, departure, and transition events ordered by announcement date, newest first. Filter by company, person, role seniority, move type, or a time window. Costs one credit per returned record.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum records to return (1-100). Each returned record costs one credit.
`since`	No	Return records announced on or after this date (YYYY-MM-DD) or ISO-8601 timestamp.
`until`	No	Return records announced on or before this date (YYYY-MM-DD, inclusive) or ISO-8601 timestamp.
`cursor`	No	Opaque pagination cursor returned as pagination.nextCursor on the previous page.
`moveType`	No	Move type filters. Canonical values: appointment, promotion, departure, transition.
`personId`	No	Filter by person id.
`companyId`	No	Filter by company id.
`countries`	No	Headquarters country codes (ISO alpha-2, OR). Pass "unknown" to include companies with no country on file.
`naicsCode`	No	NAICS 2022 code for the company. Matches the code and everything beneath it, so "51" also returns 5132 and 5173. Sector ranges work: "31-33" returns all manufacturing.
`roleSeniority`	No	Role seniority filters. Canonical values: c_level, vp_level, founder.

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false. The description adds valuable behavioral detail beyond those: results are ordered newest-first by announcement date, and each returned record costs one credit. This cost disclosure is especially useful for an agent deciding how large a result set to request.

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 short sentences with no filler: purpose and ordering first, then filtering options, then cost. Every sentence adds independent value, and the most decision-relevant facts are front-loaded.

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?

For a list tool with no output schema and 10 parameters, the description covers the essential operational context: what is returned, in what order, what filters exist, and the cost model. Pagination is handled by the cursor parameter description in the schema, so the absence of explicit pagination wording in the description is not a significant gap.

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 the schema already documents all parameters. The description only restates the filter categories (company, person, role seniority, move type, time window) without adding syntax, defaults, or enum semantics beyond what the schema provides. This is the baseline score for a fully documented 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?

The description uses a specific verb and resource: 'List executive appointment, promotion, departure, and transition events.' It also specifies the ordering ('ordered by announcement date, newest first') and the filter dimensions, making it clearly distinct from sibling tools like acquisitions, funding_events, and companies.

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 description gives clear context for when to use the tool: whenever executive move events are needed, with filters for company, person, seniority, move type, or time window. It does not explicitly name sibling alternatives or state when not to use it, but the domain is clear enough that an agent can route correctly.

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

All signals tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0

Disambiguation5/5

Each tool targets a clearly distinct resource or action: event types (acquisitions, funding_events, exec_moves), entities (companies, investors), and watchlist operations. The watchlist CRUD commands are separated by function, and company_timeline is clearly scoped to a single company's full history.

Naming Consistency4/5

Watchlist tools consistently use verb_noun (create_watchlist, get_watchlist, add_to_watchlist), while data lookup tools use plural nouns describing the returned entity or event (companies, investors, funding_events). The mixed convention is readable and predictable, with only company_timeline deviating from both patterns.

Tool Count5/5

With 11 tools, the server is well-scoped for its domain: company/event data search plus watchlist management. Each tool has a defined role and the count feels neither sparse nor bloated.

Completeness4/5

The toolset covers the core domain well: company and investor search, major event types, company timelines, and full watchlist membership management. A notable minor gap is the absence of a delete_watchlist tool, since create/list/get/add/remove exist for watchlists.

Resources

Need Help?