Skip to main content
Glama

invoke

Proxy Gemini (Vertex AI) completions wrapped in OpenTelemetry trace spans; returns the answer plus the trace/span id.

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>"
    },
    "name": "invoke"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesJSON request for this capability (the same body you'd send as an A2A message).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose real behavior: an outbound call to Vertex AI, side-effect creation of OpenTelemetry trace spans, and a return value of answer plus trace/span id. However, it omits credential/auth requirements for Vertex AI, error and rate-limit behavior, and whether model or generation settings can be controlled.

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?

It is a single front-loaded sentence with no filler, packing capability, upstream provider, tracing behavior, and return shape together. It could be marginally clearer with explicit sentence breaks, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

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

For a tool with a free-form JSON input, no annotations, and no output schema, the definition does cover the return value and the tracing side effect. It falls short on auth expectations, request-body shape, and failure modes, which an agent would need before invoking a proxied external AI service.

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 description coverage is 100%, so the single 'input' parameter is already documented in the schema and the baseline of 3 applies. The description adds no meaning about what shape the free-form JSON request body should take, which is a notable gap given the parameter is an opaque JSON blob.

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 names a concrete verb and resource: it proxies Gemini (Vertex AI) completions and returns the answer with a trace/span id. That is far more specific than the generic tool name 'invoke' and clearly separates it from a sibling like 'selftest', though it never explicitly contrasts with that sibling.

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?

There is no when-to-use or when-not-to-use guidance, no mention of the 'selftest' sibling, and no stated preconditions for calling it. An agent must infer from the description alone that this is the tool for actual model completions rather than diagnostics.

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