Resolves stock tickers to SEC CIK numbers, recent 10-K/10-Q/8-K filings, and entity metadata.
Scored across 2 tools
The two tools serve completely separate purposes: one inspects an agent's wallet/billing state, the other retrieves SEC company intelligence for a ticker. Descriptions explicitly cross-reference each other and state when NOT to use each, so misselection is unlikely.
Both names follow a strict get_<subject>_<object> snake_case pattern: get_agent_wallet_status and get_public_company_sec_intel. The verb and casing conventions are identical across the set.
Only two tools exist, and only one performs the server's stated core function (SEC intelligence); the other is auxiliary billing. Despite describing a large domain (10,000+ tickers, filings, payments), the surface is too thin for the scope.
Only ticker-to-CIK lookup plus recent filings is offered, with no filing content retrieval, search, or comparison operations. The descriptions also reference submitting payments via 'other tools on this server' for top-ups, but no such payment tool exists, leaving a dead end.
Inspect an agent's account ledger: remaining free trial calls (out of 5), prepaid USD balance, cumulative spend, total API calls, and total LLM tokens saved. WHEN TO USE: Call before a batch of paid tool executions or after completing a Stripe or USDC top-up to confirm your balance. WHEN NOT TO USE: Do not use to process web content, execute marketplace tools, or submit payments; use the other tools on this server for execution. PARAMETER INTERACTIONS: Omit agent_id to inspect the default trial account derived from your client IP, or pass your explicit agent_id or agd_pass_ session key to check a specific funded wallet. Free and read-only: never charges a fee or consumes a free trial call. Example: get_agent_wallet_status(agent_id='example')
| Name | Required | Description | Default |
|---|---|---|---|
| agent_id | No | Optional Agent ID or agd_pass_ session key to inspect. Omit to check the default wallet derived from your client IP. |
| Name | Required | Description |
|---|---|---|
| data | No | Structured tool output payload. |
| status | Yes | Execution status ('ok' or 'payment_required'). |
| roi_proof | No | Token compression and cost-savings verification metrics. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds real context beyond that: it never charges a fee or consumes a free trial call, and the default wallet is derived from the caller's client IP. It does not discuss rate limits or caching, but the cost/free-trial guarantee is meaningful behavioral disclosure.
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?
Front-loaded with the ledger contents, then structured WHEN TO USE / WHEN NOT TO USE / PARAMETER INTERACTIONS / Example. The labeled sections make it scannable, though the repetition of the read-only guarantee and the worked example add a little bulk.
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?
An output schema exists, so return-value detail is optional, yet the description still names the key fields. With a single optional parameter, no nested objects, and annotations covering safety, an agent has everything needed to invoke it correctly.
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?
Schema description coverage is 100%, so the baseline is 3. The description goes slightly further by naming the agd_pass_ session-key form and framing the two modes as an interaction (omit for IP-derived trial account vs. pass explicit agent_id/session key for a funded wallet), which aids selection even though the schema states the omit behavior.
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?
States a specific verb (inspect) and resource (agent's account ledger) and enumerates exactly what is returned: trial calls out of 5, prepaid USD balance, cumulative spend, total API calls, tokens saved. This clearly separates it from the sibling web-content tools (distill_webpage, extract_structured_data, recon_webpage_skeleton), which operate on webpages rather than wallet state.
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?
Explicit WHEN TO USE (before paid tool batches, after a Stripe or USDC top-up) and WHEN NOT TO USE (not for processing web content, executing marketplace tools, or submitting payments). The exclusion clause routes the agent back to the other server tools for execution, so the alternative is named.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Resolves all 10,000+ US public stock tickers to SEC CIK numbers, recent 10-K/10-Q/8-K filings, and entity metadata. WHEN TO USE: Call get_public_company_sec_intel when your task requires deterministic sec-intel analysis for ticker; use get_agent_wallet_status to check your remaining free trial quota or prepaid balance. WHEN NOT TO USE: Do not use for unrelated domains or binary media. PARAMETER INTERACTIONS: Pass the target ticker as a non-empty string; omit agent_id and tx_hash during your 5 free trial calls, or supply agent_id (agd_pass_...) / tx_hash for paid execution. Read-only and idempotent; results are cached for 1 hour (<5ms cache hit). $0.01 per call. Pricing: the first 5 calls per agent_id are free and failed calls are never charged. After 5 calls, the tool returns a payment-required quote (not a fatal error) with a $2 Stripe top-up link and Base/Solana USDC addresses; complete payment, then retry with your agd_pass_ key in agent_id or pass tx_hash. Example: get_public_company_sec_intel(ticker='example')
| Name | Required | Description | Default |
|---|---|---|---|
| ticker | Yes | Public stock ticker symbol (e.g. NVDA, MSFT, AAPL, PLTR). | |
| tx_hash | No | Optional on-chain Base Mainnet (0x...) or Solana SPL USDC transaction hash. Omit unless settling an individual call directly on-chain instead of using an agd_pass_ key in agent_id. | |
| agent_id | No | Optional agent identifier or prepaid agd_pass_ session key. Omit during your 5 free trial calls to use an ID automatically derived from your client IP, or pass your agd_pass_ key after topping up. |
| Name | Required | Description |
|---|---|---|
| data | No | Structured tool output payload. |
| status | Yes | Execution status ('ok' or 'payment_required'). |
| roi_proof | No | Token compression and cost-savings verification metrics. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, but the description adds substantial non-obvious behavior: 1-hour caching (<5ms hits), $0.01 per call, 5 free trial calls per agent_id, failed calls never charged, and a payment-required quote (explicitly a non-fatal response) with top-up instructions. Minor deduction for not stating result freshness beyond cache TTL.
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?
Well front-loaded: purpose first, then labeled usage, parameter, and pricing sections. However the free-trial/payment flow is restated three times (trial-call note, pricing paragraph, and closing example), so several sentences do not fully earn their place.
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?
An output schema exists, so return-format detail is unnecessary; the description covers everything else an agent needs — cost, trial limits, caching, and the exact recovery path after a payment-required response. Nothing required for correct invocation is missing.
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?
Schema coverage is 100%, so each parameter's type and constraints are already documented, giving a baseline of 3. The description goes further by specifying the interaction pattern: pass a non-empty ticker, omit agent_id/tx_hash during the free trial, and supply agd_pass_ or tx_hash only for paid execution — workflow meaning the schema alone doesn't convey.
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?
Names a concrete verb and resource set — resolving US tickers to SEC CIK numbers plus 10-K/10-Q/8-K filings and entity metadata. This is unmistakably distinct from the only sibling, get_agent_wallet_status, which the description itself identifies as the billing/quota tool.
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?
Explicit WHEN TO USE and WHEN NOT TO USE blocks, including a named alternative (get_agent_wallet_status) for quota checks and an explicit exclusion for unrelated domains/media. The condition that selects this tool is stated without inference.
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.
get_agent_wallet_status1 field changedInput schema / examplesAdded value: +[
+ {
+ "agent_id": "example"
+ }
+]get_public_company_sec_intel1 field changedInput schema / examplesAdded value: +[
+ {
+ "ticker": "example"
+ }
+]get_agent_wallet_status6 fields changedInput schema / additionalPropertiesPrevious value: -trueNew value: +falseInput schema / properties / agent_id / descriptionPrevious value: -"Agent ID or agd_pass_ key to look up. Omit it to see the ID derived from your IP and client."New value: +"Optional Agent ID or agd_pass_ session key to inspect. Omit to check the default wallet derived from your client IP."Input schema / properties / agent_id / maxLengthAdded value: +256Input schema / properties / agent_id / minLengthAdded value: +1Input schema / properties / tx_hashRemoved value: -{
- "description": "Not needed; this tool is free.",
- "type": "string"
-}Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "data": {
+ "description": "Structured tool output payload.",
+ "type": "object"
+ },
+ "roi_proof": {
+ "description": "Token compression and cost-savings verification metrics.",
+ "type": "object"
+ },
+ "status": {
+ "description": "Execution status ('ok' or 'payment_required').",
+ "type": "string"
+ }
+ },
+ "required": [
+ "status"
+ ],
+ "type": "object"
+}get_public_company_sec_intel8 fields changedInput schema / additionalPropertiesPrevious value: -trueNew value: +falseInput schema / properties / agent_id / descriptionPrevious value: -"Your agent ID, or the agd_pass_ key you got from a payment. It tracks your free calls and credit, so treat it like a password. Omit it to use an ID derived from your IP and client."New value: +"Optional agent identifier or prepaid agd_pass_ session key. Omit during your 5 free trial calls to use an ID automatically derived from your client IP, or pass your agd_pass_ key after topping up."Input schema / properties / agent_id / maxLengthAdded value: +256Input schema / properties / agent_id / minLengthAdded value: +1Input schema / properties / tx_hash / descriptionPrevious value: -"Use only after paying on-chain: the Base (0x...) or Solana USDC transfer hash. It is verified on-chain before the call runs, and any overpayment is returned as an agd_pass_ credit key."New value: +"Optional on-chain Base Mainnet (0x...) or Solana SPL USDC transaction hash. Omit unless settling an individual call directly on-chain instead of using an agd_pass_ key in agent_id."Input schema / properties / tx_hash / maxLengthAdded value: +256Input schema / properties / tx_hash / minLengthAdded value: +10Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "data": {
+ "description": "Structured tool output payload.",
+ "type": "object"
+ },
+ "roi_proof": {
+ "description": "Token compression and cost-savings verification metrics.",
+ "type": "object"
+ },
+ "status": {
+ "description": "Execution status ('ok' or 'payment_required').",
+ "type": "string"
+ }
+ },
+ "required": [
+ "status"
+ ],
+ "type": "object"
+}get_agent_wallet_status2 fields changedInput schema / properties / agent_id / descriptionPrevious value: -"Optional Agent ID or Session Pass (agd_pass_...)"New value: +"Agent ID or agd_pass_ key to look up. Omit it to see the ID derived from your IP and client."Input schema / properties / tx_hash / descriptionPrevious value: -"Optional Base (0x...) or Solana USDC tx hash"New value: +"Not needed; this tool is free."get_public_company_sec_intel3 fields changedInput schema / properties / agent_id / descriptionPrevious value: -"Optional Agent ID or Session Pass (agd_pass_...)"New value: +"Your agent ID, or the agd_pass_ key you got from a payment. It tracks your free calls and credit, so treat it like a password. Omit it to use an ID derived from your IP and client."Input schema / properties / ticker / descriptionPrevious value: -"Public stock ticker symbol (e.g. NVDA, MSFT, AAPL, PLTR)"New value: +"Public stock ticker symbol (e.g. NVDA, MSFT, AAPL, PLTR)."Input schema / properties / tx_hash / descriptionPrevious value: -"Optional Base (0x...) or Solana USDC tx hash"New value: +"Use only after paying on-chain: the Base (0x...) or Solana USDC transfer hash. It is verified on-chain before the call runs, and any overpayment is returned as an agd_pass_ credit key."get_agent_wallet_status5 fields changedInput schema / additionalPropertiesPrevious value: -falseNew value: +trueInput schema / properties / agent_id / descriptionAdded value: +"Optional Agent ID or Session Pass (agd_pass_...)"Input schema / properties / agent_id / maxLengthRemoved value: -99999Input schema / properties / agent_id / minLengthRemoved value: -1Input schema / properties / tx_hashAdded value: +{
+ "description": "Optional Base (0x...) or Solana USDC tx hash",
+ "type": "string"
+}get_public_company_sec_intel3 fields changedInput schema / additionalPropertiesPrevious value: -falseNew value: +trueInput schema / properties / agent_idAdded value: +{
+ "description": "Optional Agent ID or Session Pass (agd_pass_...)",
+ "type": "string"
+}Input schema / properties / tx_hashAdded value: +{
+ "description": "Optional Base (0x...) or Solana USDC tx hash",
+ "type": "string"
+}Resolves all 10,000+ US public stock tickers to SEC CIK numbers, recent 10-K/10-Q/8-K filings, an.
Get a US company's SEC filings and headline financials from EDGAR. $0.002/call via x402.
SEC EDGAR 10-K/10-Q/8-K filings and XBRL company facts by ticker, CIK or company name.
Search SEC EDGAR filings, financial statements, and company data.
Add one secure layer between your agents and this server.