Skip to main content
Glama

Why was this person picked?

sdr_get_person_detail

Read-only. Provenance of one contact: hunter, query, triggering signal, scores and the reasoning chain. Needs the search_id the contact belongs to.

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": {
      "id": "<id>",
      "search_id": "<search_id>"
    },
    "name": "sdr_get_person_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesContact id
search_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / id / description
      Previous value: -"Person (persona) id"New value: +"Contact id"
    • addedInput schema / properties / id / format
      Added value: +"uuid"
    • addedInput schema / properties / search_id
      Added value: +{
      +  "format": "uuid",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "id"
      -]New value: +[
      +  "id",
      +  "search_id"
      +]
  2. First observed

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description does carry the key trait that this is a non-mutating read ('Read-only.') and that it is scoped to a search. It omits any error behavior (e.g. what happens if the contact is not in that search), rate limits, or permission needs, leaving meaningful gaps for a no-annotation tool.

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 short sentences, front-loaded with the safety trait, then the payload, then the dependency. No filler or redundancy.

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?

There is no output schema, so the description takes on the job of naming the returned content, and it does so concretely (hunter, query, signal, scores, reasoning chain). It is only slightly thin on failure modes and on how the two ids relate beyond the stated ownership.

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 50%: `id` is documented as 'Contact id' but `search_id` is bare. The description compensates by explaining that search_id is the search the contact belongs to, which is exactly the missing semantic. It does not add anything for `id`, keeping it below a 5.

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 concrete operation on a specific resource: retrieving the provenance (hunter, query, triggering signal, scores, reasoning chain) of a single contact. This distinguishes it from aggregation siblings like sdr_company_detail or sdr_get_research, though it never names an alternative directly.

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?

Gives an important prerequisite ('Needs the search_id the contact belongs to') which tells the agent it cannot call this standalone. However, it never states when to prefer this over sdr_company_detail, sdr_get_research, or sdr_activity_feed, so usage is only implied by the described payload.

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