Skip to main content
Glama

Company profile from its website in one call

company_info
Read-only

Company profile from its website in one call: name, description, logo, founding date, address, phones, emails, social profiles and links to about/contact/careers/pricing pages, from structured data and the page. Takes 1-4 s. Free: 20 calls/day per user across free tools, no payment needed. Above that: $0.005 per call (x402, USDC on Base).

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": {
      "url": "<url>"
    },
    "name": "company_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL
paymentNox402 payment: the base64 PAYMENT-SIGNATURE value signed for the requirements returned by an unpaid call (USDC on Base, gasless). Omit on the first call to get the price and requirements.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description is not obligated to explain safety, but it goes well beyond them: 1-4 s latency, a 20 calls/day free quota across free tools, and a $0.005 overage charged via x402/USDC with the first unpaid call returning price and requirements. The only gap is that it does not describe failure modes (unreachable site, no structured data found) or what a minimal/partial profile looks like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the resource and its full output list, followed by timing and then cost/payment mechanics. Every clause carries decision-relevant information; nothing is repeated from the title or schema.

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 correctly takes on the job of enumerating returned fields, and it also covers the non-obvious two-step payment handshake and quota. For a two-parameter, read-only fetch tool, an agent has everything it needs to call it correctly on the first attempt.

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 real meaning the schema does not: that the payment field is optional on the first call, which exists to return price and requirements before a signed retry, and that pricing is per-call above the free quota. It does not add anything about URL constraints (e.g., what happens with redirects or non-company domains) beyond the schema's 'Public http(s) URL'.

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 concrete verb+resource (extract a company profile from a given website URL) and enumerates exactly what comes back: name, description, logo, founding date, address, phones, emails, social profiles, and about/contact/careers/pricing links. That field-level enumeration lets an agent distinguish it from narrower siblings such as contacts or meta without opening a schema.

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

Usage Guidelines3/5

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

The 'in one call' framing implies this is the bundled alternative to field-specific siblings, and the latency plus free-tier/quota notes help the agent decide if a call is affordable. However, it never names an alternative tool or states a condition under which an agent should use something else instead, so selection guidance is only implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.