Skip to main content
Glama
Sign In
mcp-gauge

mcp-gauge

by CHANGCHINFU
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Regulatory-filing triangle: corporate distress & insider ($0.10)

gauge_filing_check

Evaluate regulatory filings for a company ticker: cross-check 8-K material events, NT late filings, and Form 4 insider trades to identify distress signals.

Instructions

Regulatory-filing triangle for a company: 8-K material events (item severity — bankruptcy/default/restatement/delisting = critical) + NT late-filing delinquency (distress leading indicator) + Form 4 insider net open-market buy/sell + cross-validation (do insiders confirm the distress by selling or contradict it by buying). All official SEC EDGAR. For event-driven/activist/short funds, quant funds, credit & distressed analysts. Costs $0.10 USDC on Base. entity = ticker e.g. AMC, CVNA, GME.

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": {
      "entity": "<entity>"
    },
    "name": "gauge_filing_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
entityYesticker from watchlist, e.g. AMC, CVNA, GME, BA (see gauge_preview filing_watchlist)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description bears full responsibility. It mentions 'All official SEC EDGAR' and the cost, but does not disclose potential error conditions, data freshness, rate limits, or authentication requirements. This is adequate but leaves some behavioral gaps.

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?

The description is a single paragraph that efficiently conveys the tool's purpose, components, users, and cost. Every sentence adds value, though it could be slightly more structured (e.g., bullet points) without losing conciseness.

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?

Given the absence of an output schema and minimal annotations, the description adequately explains the tool's inputs and intended analysis. However, it does not describe what the tool returns (e.g., a report, JSON, or visualization), leaving the agent to infer the output from the purpose.

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

Parameters4/5

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

The only parameter 'entity' is described in the schema as 'ticker from watchlist' with examples. The description reinforces this with 'entity = ticker e.g. AMC, CVNA, GME' and references another tool, adding useful context beyond the 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 clearly identifies the tool as a regulatory-filing triangle combining 8-K, NT late-filing, and Form 4 insider transactions with cross-validation. It specifies the intended users (event-driven, activist, etc.) and distinguishes it from sibling tools which cover unrelated domains like crop drought or flood risk.

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 states the target users and cost, but does not explicitly state when not to use this tool or provide direct comparisons to sibling tools. However, sibling tools are for different domains, so the context implies appropriate use.

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

Deploy Server

Other Tools