Skip to main content
Glama

Descovo — B2B contact data

get_endpoint_details_full

Get COMPLETE schema and details for a specific API operation.

Use this BEFORE calling an API to understand exactly what parameters are needed.

Args: operationId: The operation ID (e.g., "syncQuickContactReveal")

Returns: Complete schema including all required/optional fields, request body schema, response schema, and example usage.

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": {
      "operationId": "<operationId>"
    },
    "name": "get_endpoint_details_full"
  }
}

Input Schema

NameRequiredDescriptionDefault
operationIdYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden alone. It discloses the return contents (required/optional fields, request body schema, response schema, example usage) and implies a read-only lookup, but says nothing about failure behavior for an unknown operationId, latency, or whether results can be cached. Adequate but with real gaps for a zero-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.

Conciseness4/5

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

The purpose leads, followed by a usage directive and clearly labeled Args/Returns blocks, so an agent can scan it quickly. The capitalized "COMPLETE" is mildly promotional, and the Returns block partly restates what the output schema already declares, but nothing is genuinely wasted.

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?

For a one-parameter lookup tool with an output schema present, the definition covers everything needed to invoke it correctly: what it returns, when to call it, and the operationId format. The only omission, error behavior on an invalid ID, is minor and not required for correct invocation.

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 0% and the single parameter has no description in the schema, so the description must compensate. It does partially by giving a concrete example value ("syncQuickContactReveal"), clarifying the operationId format, but it never says where an operationId comes from or whether it is case-sensitive.

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 specific verb (Get) and resource (COMPLETE schema and details for a specific API operation), scoped to a single operationId. This clearly separates it from list_all_endpoints and search_endpoints, which surface many operations, and it positions itself as the detail lookup for a single one.

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

Usage Guidelines4/5

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

Gives an explicit when-to-use rule: call this BEFORE invoking an API to learn what parameters are needed. That is a clear workflow cue, but it names no alternative (e.g., call_operation) and states no when-not condition, such as already having the schema cached.

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