Skip to main content
Glama

SourceGeek

Enrich a person or company

enrich_entity
Read-only

Enrich a known entity (description or URL) with specific structured string fields and citation-backed reasoning. Starts a paid run with an external research provider and spends the workspace's credits.

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": {
      "input": "<input>",
      "fields": "<fields>"
    },
    "name": "enrich_entity"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesEntity name, description, or canonical URL to enrich.
fieldsYesFields to populate (max 10).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Going well beyond the annotations, the description discloses that the call starts a paid run with an external research provider and consumes the workspace's credits — a cost signal the readOnlyHint/openWorldHint annotations do not capture. What it does not state is whether the run is synchronous or asynchronous, how long it takes, or what happens on failure or insufficient credits.

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 with zero filler: the what comes first and the cost consequence is appended as the key caveat. 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.

Completeness4/5

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

For a two-parameter, fully documented, annotation-covered tool this is nearly complete: purpose, input forms, field limit, and cost are all covered. The one remaining gap is return behavior — with no output schema, the description could say more about how the citation-backed reasoning is delivered.

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%, so both parameters are already well documented, giving a baseline of 3. The description adds a small amount of meaning by specifying that the populated fields are structured string fields with citation-backed reasoning, which constrains the result type beyond what the schema states.

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?

The description gives a specific verb and resource ("Enrich a known entity") plus acceptable input forms (description or URL), so an agent immediately knows this is an enrichment tool rather than one of the employee_* lookup siblings. It stops short of explicitly contrasting itself with those siblings, which keeps it at 4 rather than 5.

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?

"Enrich a known entity" implies the precondition that the entity is already identified, and that is useful implied guidance. However, there is no explicit when-to-use versus when-not guidance, no mention of what to do if the entity is unknown, and no named alternative for a plain lookup.

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