Skip to main content
Glama
Hermoso

Hermoso

Official

Run any Hermoso tool by name

call_tool
Destructive

Run any Hermoso tool by name, including paid-campaign, analytics and channel-admin tools missing from your host's starting list. Validates arguments against each tool's schema and returns the expected parameters on error.

Instructions

Run ANY Hermoso tool by name — including the paid-campaign, analytics and channel-admin tools that are not in this session's starting list — with the same permissions, the same account and the same result as calling it directly. Get the exact name and its args from find_tools first. This is the route on hosts that cannot reload their tool list mid-conversation (claude.ai, ChatGPT): enable_tools switches a group on server-side, but such a host keeps the list it fetched at connect time. Arguments are validated against the tool's own schema and a mistake is answered with the expected parameters, not a silent default. Refused by name, with the way out, when the tool needs a connector this workspace has not made or is withheld by the host's own policy.

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
argsNothe tool's arguments as an object, exactly as its own schema takes them
nameYesthe tool name exactly as find_tools returned it, e.g. create_meta_lead_form
contextNooptional: the user's underlying goal in one short sentence, for analytics only (no names, contact details or URLs); every tool also accepts it directly
revisionNothe revision find_tools gave for this tool; a changed tool is refused unrun, with its current params

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.532
    • addedInput schema / properties / context
      Added value: +{
      +  "description": "optional: the user's underlying goal in one short sentence, for analytics only (no names, contact details or URLs); every tool also accepts it directly",
      +  "type": "string"
      +}
    • addedInput schema / properties / revision
      Added value: +{
      +  "description": "the revision find_tools gave for this tool; a changed tool is refused unrun, with its current params",
      +  "type": "string"
      +}
  2. Addedv0.1.209

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, openWorldHint=true and non-idempotent, and the description adds real context beyond that: identical permissions/account/result as a direct call, schema-validated args with an error listing expected parameters rather than a silent default, revision mismatch refused unrun, and name-based refusal when a connector is missing or host policy withholds the tool. It stops short of warning that underlying tools may be destructive, leaving that inference to the underlying tool's own definition.

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?

Front-loaded with the core action in the first clause, then progressively adds routing, validation and failure behavior. Dense and mostly waste-free, though the host-specific parenthetical about claude.ai and ChatGPT is slightly digressive for the space it occupies.

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

Completeness5/5

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

For a dispatcher with a nested args object and no output schema, the description covers the essentials an agent needs: where to get name/args, what the result will be, how argument errors surface, and when it refuses. Nothing material for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds genuine meaning: name must match find_tools output exactly, args are validated against the target tool's own schema, and revision causes an unrun refusal with the current params returned. The optional context parameter is left to the schema, which is acceptable given full coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Run ANY Hermoso tool by name') and immediately scopes it to tools not in the session's starting list, which separates it from find_tools and enable_tools. An agent can tell what this does without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit prerequisites ('Get the exact name and its args from find_tools first') and an explicit when-to-use-this-instead rule: on hosts that cannot reload their tool list mid-conversation, enable_tools only flips a group server-side while the host keeps its connect-time list. That is a concrete routing condition against a named sibling.

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

Deploy Server

Other Tools