Skip to main content
Glama

Gate Invoke

gate_invoke

Invokes any Gate tool by name with arguments when a tool is missing from tools/list, enabling catalog-mode access to unlisted Gate-MCP tools.

Instructions

Catalog mode: call any Gate tool by name with args. Use for tools not in tools/list. See gate_help.

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": {
      "tool": "<tool>"
    },
    "name": "gate_invoke"
  }
}

Input Schema

NameRequiredDescriptionDefault
argsNoArguments object for the target tool
toolYesGate tool name, e.g. gate_memory or gate_clean_response

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.12

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden. It says the tool dispatches arbitrary Gate tools but does not disclose side-effect potential, permissions, error behavior, whether the target tool's annotations apply, or what output the caller should expect.

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 definition is short and front-loaded: it gives the dispatch purpose first, then the usage condition, then points to help. There is little waste, though 'Catalog mode' could be clearer.

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 generic invoker with nested args and no annotations or output schema, the description gives enough to attempt a basic call and points to gate_help for discovery. It remains insufficient for understanding side effects, failure modes, or result handling, which matters for a tool that can invoke arbitrary siblings.

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 input schema already documents both 'tool' and 'args'. The description only restates that a tool is called by name with args and adds no format, error, or nesting semantics 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 a specific dispatch action: call any Gate tool by name with args. It distinguishes itself from listed sibling tools by saying it is for tools not in tools/list, though the phrase 'Catalog mode' is somewhat jargon-like.

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?

Usage is explicitly scoped to tools not in tools/list, which tells the agent when to choose this generic invoker over directly calling a listed tool. It points to gate_help for discovery, but does not explicitly state the inverse case or describe fallback behavior if the named tool is unknown.

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