Skip to main content
Glama

Agent Utility Suite (x402)

by io.github.vanakenj45
OverviewDiscussionsAdmin

Company profile

company_profile
Read-onlyIdempotent

Answers "Who is behind stripe.com?", "What does this company do, where is it based and who runs it?" or "Is it public, and what is its ticker?". Give a website domain (or any URL), a company name, a ticker or a CIK. Returns one profile combining: SEC EDGAR for public companies (legal name, tickers, exchanges, CIK, SIC industry, state of incorporation, fiscal year end, business address, phone, filer category, former names), Wikidata (founded, founders, CEO, headquarters, country, employees with date, industries, official website), a short Wikipedia description (with its URL for attribution), and the domain's email provider (from MX records) and registration date and registrar (RDAP). Works for private companies too (Wikidata and the domain). sources says which sources answered. For public companies, next_calls lead to their financials, 8-K events and insider trades. A name matching several SEC registrants returns the candidates, free; no company found is a 404, free. You are only charged when a result is returned: invalid input (400) and upstream failures (4xx/5xx) are not settled. Costs $0.005 USDC per call via x402. Paid per call with x402 inside MCP (see the server instructions).

Input Schema

NameRequiredDescriptionDefault
cikNoSEC Central Index Key, e.g. 320193. Use this, `ticker` or `company`.
viaNoOptional: the tool whose next_calls suggested this call (filled in for you).
domainNoThe company's website domain or any URL on it, e.g. "stripe.com". Use this, `company`, `ticker` or `cik`.
tickerNoUS stock ticker, e.g. AAPL, MSFT, BRK-B. Use this, `cik` or `company`.
companyNoCompany name, e.g. "Apple" or "Coca-Cola". Use this, `ticker` or `cik`; a name matching several companies returns their tickers, free.

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?

Annotations already declare read-only, idempotent, open-world and non-destructive, so the bar is lower; the description nonetheless adds substantial behavioral detail beyond them — how `sources` reports which providers answered, the free 404/name-collision cases, the non-settled 400/4xx/5xx cases, and the $0.005 USDC x402 charge only on returned results.

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 user-facing purpose before the dense source inventory, and every sentence carries information (inputs, return composition, error/billing behavior). It is on the long side for a single-paragraph description, but the length is justified by the tool's complexity.

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 carries the return-value burden and does so fully: it enumerates the EDGAR, Wikidata, Wikipedia, MX and RDAP fields and explains `sources`. Combined with its billing and error disclosure, an agent has everything needed to call and interpret it.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning: any URL on the domain is acceptable, not just the bare domain, and a `company` name matching several SEC registrants returns candidates (free) rather than failing. That clarifies behavior the schema's 'Use this, `ticker` or `company`' notes do not.

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+resource and even frames it as the literal questions it answers ('Who is behind stripe.com?', 'Is it public, and what is its ticker?'). The input forms (domain/name/ticker/CIK) and the returned content are enumerated, letting an agent distinguish it from sibling tools like domain_enrich or company_dossier.

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?

Gives clear when-to-use context: works for private companies too, and for public companies 'next_calls lead to their financials, 8-K events and insider trades', which routes the agent onward. It does not, however, explicitly contrast itself against close siblings such as company_dossier, domain_enrich or counterparty_check.

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
Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources