Skip to main content
Glama

invoke

Turn a prompt + a field schema into validated, typed JSON (Instructor over Gemini 2.5 Flash on Vertex AI).

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.1/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, and it does disclose meaningful traits: this is an LLM-backed call (Gemini 2.5 Flash on Vertex AI) that returns validated, typed output via Instructor. It does not cover failure behavior, retry semantics, latency or cost implications of an inference call, or whether the field schema must be JSON Schema specifically.

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?

One front-loaded sentence plus a parenthetical implementation note, with no filler. The parenthetical earns its place by naming the model and library, though it does not solve the more pressing gap about the request body format.

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?

For a tool whose only parameter is a free-form JSON envelope described as 'the same body you'd send as an A2A message', the description should sketch that body's shape. With no output schema and no annotations, the agent is left to guess the request structure for the one thing it must construct.

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 100% for the single 'input' parameter, so the baseline is 3. The description adds a partial hint about what goes inside that opaque JSON string (a prompt and a field schema), but never names the keys, encoding, or schema dialect, so the wrapper format remains largely undiscoverable.

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 specific transformation: prompt + field schema in, validated typed JSON out. An agent immediately knows this is structured extraction, not a generic dispatcher despite the generic name 'invoke'. It does not differentiate from the sibling 'selftest', but the core purpose is unambiguous.

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 alternatives, and no stated preconditions for calling it. The agent must infer from the name and the single sentence that this is the general entry point for all capability requests.

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.