Skip to main content
Glama

Call a flayr tool by name

call_tool
Destructive

Runs any flayr tool, listed or not, with the same scopes, plan checks and confirmations as calling it directly. The inner tool's own risk applies: confirm PUBLISHES or DESTRUCTIVE tools with the user first.

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe tool name from search_tools or enable_toolset, e.g. "ads_campaigns_list".
argumentsNoThe tool's arguments as an object, e.g. {"brandId": "b_123"}. Omit for none.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, but the description adds genuinely new context: the call inherits the inner tool's scopes, plan checks and confirmations, and the inner tool's own risk classification governs. The instruction to confirm PUBLISHES or DESTRUCTIVE tools with the user is concrete operational guidance beyond the annotation flags. It does not say what happens on an invalid or unauthorized tool name.

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, zero filler, and the delegation semantics are front-loaded before the risk-handling caveat. Every clause carries information an agent needs before dispatching an arbitrary tool.

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

Completeness4/5

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

For a meta-dispatch tool with a tiny schema, the description covers the essentials: what it does, that behavior is inherited from the target tool, and the confirmation requirement for dangerous targets. Minor gaps remain around error behavior for unknown names and whether argument validation is the caller's responsibility, but nothing critical is absent.

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 both `name` and `arguments` are already documented, including an example for each. The description adds nothing about how to shape `arguments` (e.g., that it must match the target tool's schema, obtainable via describe_tool), so it neither compensates nor detracts — the baseline 3 applies.

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 verb and scope: "Runs any flayr tool, listed or not," which makes clear this is a generic proxy invoker rather than one of the concrete siblings like publish or get_post. It does not explicitly contrast itself with describe_tool or search_tools, but the "listed or not" phrasing implicitly separates discovery tools from execution.

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?

"Listed or not" implies the primary use case: invoking tools that aren't directly exposed in the current toolset, and the schema points to search_tools/enable_toolset as the source of names. What's missing is an explicit preference rule (e.g., "prefer calling the tool directly when it is already exposed"), so an agent must infer the ordering itself.

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