API Tool Calls

Company Info Finder

company_facts

Read-onlyIdempotent

Read a business's own home, about and contact pages and return its name, address, phone, email, founding year and what it does, each with the page it came from. Page text goes to a language model: with no key, a small shared free daily allowance (Google Gemini); with an X-OpenRouter-Key header, the caller's OpenRouter key.

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_facts"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	The business's public http or https homepage URL.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 4, 2026
RemovedOct 4, 2026
AddedOct 2, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover readOnly/openWorld/idempotent/non-destructive, so the safety profile is handled. The description adds genuinely useful behavior beyond them: page text is sent to a language model, there is a small shared free daily allowance without a key, and an X-OpenRouter-Key header lets callers use their own key. That discloses rate-limit and auth behavior an agent needs.

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?

Two tight sentences: the first front-loads what it does and returns, the second carries the LLM/auth/allowance detail. No filler, and the purpose is stated before the operational caveats.

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?

No output schema exists, yet the description enumerates the returned fields and their provenance, plus the auth and rate-limit context. For a one-parameter read-only tool with rich annotations, nothing an agent needs to invoke it correctly is missing.

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% and the url field is fully documented, so the baseline would be 3. The description adds meaning beyond the schema by clarifying that the single URL is the entry point and the tool also reads the business's about and contact pages, so the agent understands one homepage URL fans out to multiple pages.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a precise verb and resource ('Read a business's own home, about and contact pages') and enumerates the exact fields returned, so an agent knows exactly what it gets. It is clearly distinct from calculator siblings, but it never names or differentiates itself from web-fetching siblings like page_check or page_to_markdown, which is the closest ambiguity.

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 purpose implies when to reach for it (when you need business identity details from a URL), but there is no explicit when-to-use/when-not guidance and no mention of the alternative page tools. The second sentence adds operational context (keys, allowance) but not selection guidance.

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

All API Tool Calls tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?