Skip to main content
Glama

Agent Utility Suite (x402)

by io.github.vanakenj45
OverviewDiscussionsAdmin

Company dossiers in batch (portfolio screen)

company_dossier_batch
Read-onlyIdempotent

Answers "Which of my holdings has a problem?" or "Screen these tickers for red flags before the open". Give up to 10 tickers, CIKs or company names. Returns a ranking (most red flags first, then amber) with each company's flags and one-paragraph summary, and every company's full dossier: profile, four fiscal years of financials and the latest quarter, the last five 8-K events, insider buying and selling over the latest 10 Form 4s, the latest 10-K/10-Q, and flags (RED: restatements, delisting notices, bankruptcy, late 10-Ks; AMBER: auditor changes, cybersecurity incidents, impairments, late 10-Qs, losses, cash burn, negative equity, shrinking revenue; GREEN: profitable growth, insider buying), each citing its filing. Priced by size: $0.03 for the first company and $0.025 for each further one (2 companies $0.055, 3 $0.08, 4 $0.105, 5 $0.13), capped at $0.15 for 6 to 10, always less than separate company_dossier calls. The 402 answer quotes the exact price for your list. Companies that cannot be found are listed in failed; if none can, you are not charged. You are only charged when a result is returned: invalid input (400) and upstream failures (4xx/5xx) are not settled. Costs $0.03 to $0.15 USDC per call via x402. Paid per call with x402 inside MCP (see the server instructions).

Input Schema

NameRequiredDescriptionDefault
viaNoOptional: the tool whose next_calls suggested this call (filled in for you).
tickersYesUp to 10 companies: tickers (e.g. "NVDA"), CIKs (e.g. 320193) or exact company names.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / via
      Added value: +{
+  "description": "Optional: the tool whose next_calls suggested this call (filled in for you).",
+  "maxLength": 64,
+  "type": "string"
+}
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes far beyond the readOnly/idempotent/openWorld annotations: it discloses the ranking order (red before amber), the exact dossier contents, the billing rules (only settled when a result returns; 400/4xx/5xx not charged; unfindable firms go to `failed`; no charge if none found), and the 402 price-quote behavior. This is exactly the behavioral context an agent needs before a paid call.

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?

Front-loads the use case and output shape before cost, which is good ordering, and every sentence carries information. It is nonetheless long and repeats the price structure twice (the enumerated per-size figures and again as 'Costs $0.03 to $0.15 USDC per call'), which slightly dilutes density.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description fully covers returns: ranking, per-company flags and summary, the dossier contents, and the `failed` bucket. Billing, failure handling, and payment mechanism are all addressed, leaving nothing an agent needs before calling.

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 coverage is 100% and the description largely restates the schema ('up to 10 tickers, CIKs or company names'), adding no format or edge-case detail beyond it. The `via` param is already documented in the schema. Baseline 3 is appropriate when the schema carries the full burden.

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?

States a specific verb and resource (batch company dossiers/portfolio red-flag screen) and immediately differentiates itself from the sibling company_dossier by noting it is 'always less than separate company_dossier calls'. The quoted use-case questions pin down exactly what job it does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Front-loads two concrete when-to-use scenarios (portfolio problem screening, pre-open red-flag triage) and explicitly compares itself to the single-company alternative on cost. The 'up to 10 tickers' bound plus the price advantage make the routing decision unambiguous.

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

All Agent Utility Suite (x402) toolsInspect
Try in Browser
Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources