Skip to main content
Glama

company_enrichment_evidence

Company enrichment with free input preflight, provider attribution and signed evidence; 0.005 USDC.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "website": "example.com"
    },
    "name": "company_enrichment_evidence"
  }
}

Input Schema

NameRequiredDescriptionDefault
lidNo
nameNo
emailNo
inputNo
phoneNo
queryNo
entityNo
pdl_idNo
personNo
regionNo
schoolNo
tickerNo
companyNoCompany name or nested input object
contactNo
countryNo
profileNo
subjectNo
websiteNo
localityNo
locationNo
last_nameNo
birth_dateNo
email_hashNo
first_nameNo
identifierNoEmail, profile URL, phone, company domain, ticker or name; interpreted by service
postal_codeNo
street_addressNo
minimum_likelihoodNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "website": "example.com"
      +  }
      +]
  2. First observed

TDQS

C2.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose two useful traits that structured fields do not: the cost (0.005 USDC) and that input validation happens before payment. However, it omits auth requirements, rate limits, idempotency, and what happens to a paid call that later fails enrichment.

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?

A single dense sentence with the core function front-loaded; no filler. It is jargon-heavy ('signed evidence', 'provider attribution') but every clause carries information.

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

Completeness2/5

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

For a 28-parameter, paid, no-annotation tool with no output schema, the description is far too thin. It never explains the return shape beyond 'signed evidence', gives no failure or refund behavior, and leaves the identity-input model undocumented for the agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 7% across 28 parameters, so the description is expected to compensate, and it does not — it says nothing about accepted identifier forms or the semantics of nested input/query/entity/company. The useful enumeration of identifiers lives in the schema's own description field, not the tool description.

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 specific verb+resource (company enrichment) and differentiates from siblings like person_enrichment_evidence, contact_enrichment_evidence, and entity_enrichment_evidence by naming the company domain. It also names the deliverables (provider attribution, signed evidence) and the price, though the pricing detail slightly crowds out the core purpose.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance and no routing to alternatives such as preflight or preflight-free schema_normalize_free. The phrase 'free input preflight' hints that validation happens first, but the agent is left to infer whether this tool should be called before or after the sibling enrichment tools.

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.

Resources