orbit-sentinel-mcp

Overview Schema Source Related Servers Discussions Admin

get_filing_trends

Read-only

Analyze regulatory filing volume trends across time periods and identify top movers by growth, enabling year-over-year comparisons and emerging-player detection.

Instructions

Get filing volume trends over time periods with optional top movers (entities with biggest changes). Use for questions about growth, trends, emerging players, or year-over-year comparisons.

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_filing_trends"
  }
}

Input Schema

Name	Required	Description
`agency`	No	Filter by agency (FCC, ITU, UN_OOSA)
`periods`	No	Number of periods (default 2, max 12)
`entity_id`	No	Entity UUID for per-entity trends
`top_movers`	No	Top N entities by biggest change
`entity_type`	No	Filter by entity type: company, individual, or government
`period_months`	No	Months per period (default 12, max 60)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1Jul 10, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=false, so the safety profile is covered. The description adds that top movers are 'entities with biggest changes' and that trends are period-based, but it does not discuss return shape, pagination, or behavior when periods are omitted. That is adequate but not rich.

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 tight sentences with zero filler, and the core purpose is front-loaded before the use-case guidance. Every phrase contributes.

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 read-only analytical tool with zero required parameters, the description covers purpose, optional top-movers behavior, and use cases well. It does not give any sense of the returned time-series structure, which would help since there is no output schema, keeping it from a 5.

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 all six parameters are already documented in the schema. The description only restates that top movers are entities with the biggest change, which the schema also says, adding little semantic depth beyond structured fields.

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 pairs a specific verb and resource ('Get filing volume trends over time periods') with the optional top-movers output, making it clearly distinct from siblings like get_filing_distribution or get_filing_detail. An agent can tell this is the longitudinal trend tool rather than a snapshot or per-filing lookup.

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?

It gives explicit use cases ('questions about growth, trends, emerging players, or year-over-year comparisons'), which is strong positive guidance. It stops short of naming a sibling to prefer for non-trend queries, so it does not reach the when-not/alternatives bar.

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