Skip to main content
Glama
Consiliency

PMCP

by Consiliency
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

gateway.invoke

Invoke tools on downstream MCP servers with schema-validated arguments and automatic output truncation to prevent oversized responses.

Instructions

Invoke a tool on a downstream MCP server. Arguments are validated against the tool schema before execution. Output is automatically truncated if too large.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
optionsNo
tool_idYesThe tool ID in format "server_name::tool_name"
argumentsNoArguments to pass to the tool (must match tool schema)
run_correlation_idNoScoped-advisor run correlation ID
seat_correlation_idNoScoped-advisor seat correlation ID
evidence_label_digestNoSHA-256 digest of the caller evidence label

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed3 schema fields changedv1.20.0
    • addedInput schema / properties / evidence_label_digest
      Added value: +{
+  "description": "SHA-256 digest of the caller evidence label",
+  "pattern": "^[0-9a-f]{64}$",
+  "type": "string"
+}
    • addedInput schema / properties / run_correlation_id
      Added value: +{
+  "description": "Scoped-advisor run correlation ID",
+  "type": "string"
+}
    • addedInput schema / properties / seat_correlation_id
      Added value: +{
+  "description": "Scoped-advisor seat correlation ID",
+  "type": "string"
+}
  2. First observedv1.18.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses validation before execution and automatic output truncation, but lacks details on error handling, idempotency, or authentication requirements.

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 sentences, no redundant information, purpose is front-loaded. Every sentence provides essential behavioral insight.

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?

Despite describing core behaviors, the description omits return value format, error handling, and how to structure the nested 'options' object. For a complex gateway proxy tool, more detail is needed.

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 83%, so the schema already describes most parameters. The description adds context about validation and truncation but does not elaborate on parameter usage beyond the schema.

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 clearly states the tool invokes a tool on a downstream MCP server, with specific actions like validation and truncation. It distinguishes from sibling tools as no other gateway tool serves a similar proxy invocation 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?

No guidance is provided on when to use this tool versus alternatives, nor any conditions or exclusions. The agent has no help in deciding context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Consiliency/pmcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server