Verify financial claims against official SEC filing and XBRL evidence.
Verify whether a company's official SEC filing supports a specific financial claim. Input ticker or CIK plus claim. Returns filing/XBRL evidence and supported, contradicted, insufficient-evidence, or explicit ambiguity/failure states. Not a market-data feed or investment advice.
| Name | Required | Description | Default |
|---|---|---|---|
| cik | No | SEC Central Index Key. Provide ticker or CIK. | |
| claim | Yes | One atomic financial claim to check against official SEC filings. | |
| period | No | Optional period hint such as latest quarter or FY2025. | |
| ticker | No | Issuer ticker symbol. Provide ticker or CIK. | |
| filing_type | No | Optional filing hint such as 10-Q or 10-K. | |
| fiscal_year | No | Optional fiscal year. | |
| fiscal_quarter | No | Optional fiscal quarter such as Q1. |
| Name | Required | Description |
|---|---|---|
| cik | Yes | |
| claim | Yes | |
| period | Yes | |
| ticker | Yes | |
| company | Yes | |
| verdict | Yes | |
| evidence | Yes | |
| period_end | Yes | |
| filing_date | Yes | |
| filing_type | Yes | |
| source_urls | Yes | |
| period_start | Yes | |
| retrieved_at | Yes | |
| source_status | Yes | |
| service_version | Yes | |
| reasoning_summary | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare read-only, idempotent, and non-destructive behavior. The description adds clarity about return states (supported, contradicted, insufficient-evidence, etc.) and disclaims financial advice, which goes beyond the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise, with two sentences covering purpose, input, output, and limitations. No redundant or filler content.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description is complete for a verification tool: it states what it verifies, the input requirements, the output evidence, and the possible result states. It also sets boundaries with the disclaimer. This suffices given the annotations and schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already describes each parameter. The description adds the relationship that 'ticker or CIK' are alternatives, which is not explicit in the schema. This improves understanding of parameter usage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states the tool's function: verifying a financial claim against official SEC filings. The verb 'verify' and resource 'SEC filing' are specific and unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides a hint on input (ticker or CIK plus claim) and explicitly states what it is not for ('Not a market-data feed or investment advice'), which helps with usage context. However, it does not explicitly mention alternatives or when to avoid using it beyond that.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
verify_sec_filing_claimClaiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such as io.github.acme/server also needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.
HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!
Add one secure layer between your agents and this server.
With only one tool, there is no possibility of selecting between overlapping tools. The tool's purpose is clearly defined and distinct by default.
The single tool name follows a clear verb_noun snake_case convention, setting a consistent pattern. There are no conflicting naming styles to confuse an agent.
A single tool is minimal and may feel thin, but it is narrowly scoped to verifying SEC filing claims. This makes it borderline rather than egregiously under-provisioned.
The tool covers the entirety of the stated purpose—verifying claims against SEC filings—with comprehensive result states. There are no obvious missing operations for this narrowly defined domain.