Descovo

by com.descovo.mcp

call_operation

Execute any Descovo API operation by operationId.

IMPORTANT:

apiKey is NOT required in the body if the MCP client sends an x-api-key header (most configs do). The backend auto-injects it.
Prefer search_endpoints() first when operation choice is ambiguous.
Use get_endpoint_details_full(operationId='...') first for complex/nested parameter shapes.

Args: operationId: The operation ID to call params: Parameters dict: {"body": {...}, "path": {...}, "query": {...}}

Returns: API response data or error details.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`params`	No
`operationId`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

TDQS

A4.8/5.0

Behavior4/5

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

Discloses key behavioral traits: auto-injection of apiKey, fallback recommendations, and return of error details. No contradictions with missing annotations.

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?

Compact, well-organized into IMPORTANT and Args sections; every sentence adds value with no redundancy.

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?

Fully covers usage, parameters, and return value (API response or error details), meeting all needs for a generic API caller tool.

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

Parameters5/5

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

Despite 0% schema coverage, the description fully explains both parameters: operationId as string and params as dict with body/path/query, adding essential structural detail.

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?

Explicitly states the tool executes 'any Descovo API operation by operationId', clearly defining its purpose and distinguishing it from sibling tools like search_endpoints and get_endpoint_details_full.

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

Usage Guidelines5/5

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

Provides explicit guidance: when to omit apiKey (auto-injection), when to prefer search_endpoints (ambiguous choice), and when to use get_endpoint_details_full (complex parameters).

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

All Descovo tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0

Disambiguation5/5

Each tool serves a distinct purpose: call_operation executes, get_endpoint_details_full provides schema, list_all_endpoints and search_endpoints discover endpoints, and list_tag_packs aids browsing. No overlap.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case, such as 'call_operation', 'list_all_endpoints', and 'search_endpoints'. No mixing of styles.

Tool Count5/5

With 5 tools, the set is well-scoped for a dynamic API gateway: discovery, details, execution, and tag-based exploration. Not too many or too few.

Completeness5/5

The tools cover the full lifecycle of interacting with an API catalog: discovery (list, search), detailed schema inspection (get_endpoint_details_full), and execution (call_operation). No obvious gaps like missing tag management.

Resources

Need Help?