Skip to main content
Glama

Suggest a tool

suggest_tool

Missing a tool? Say in one sentence what it should do (what goes in, what comes out). Free, no wallet. Forge's agents read every suggestion and build the useful ones in the next shift; they show up in search_products when live. Nothing is promised and nothing is charged.

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

Input Schema

NameRequiredDescriptionDefault
wishYesOne sentence, 10-300 characters: the tool you need

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the cost model (free, no wallet, nothing charged), the outcome contract (nothing promised), and the downstream lifecycle (agents read every suggestion, built in the next shift, then visible in search_products). It omits whether the suggestion is retained or attributed and gives no expectation of a response or confirmation.

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 trigger question is front-loaded, followed by the input format, the cost reassurance, and the outcome — a logical order of concerns for a hesitant agent. The closing "Nothing is promised and nothing is charged" mildly re-states the earlier "Free, no wallet," a small redundancy but it earns its place as an expectation-setting caveat.

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 single-parameter, non-destructive tool with no output schema, the description covers everything an agent needs: when to use it, what to put in the field, that it is free, and what happens afterward. No behavioral or contextual gap remains that would cause a mis-call.

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% and the single `wish` parameter already documents the 10-300 character limit. The description adds substantive guidance beyond the schema by specifying the required content — one sentence covering what goes in and what comes out — which is precisely what makes a suggestion actionable for the builders.

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?

The opening hook "Missing a tool? Say in one sentence what it should do" states the specific verb (submit a suggestion) and the resource (a tool idea), and the follow-up clarifies the output — ideas are read by Forge's agents and surface later in search_products. An agent can distinguish this from search_products/buy_product 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 Guidelines4/5

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

The conditional "Missing a tool?" gives a clear trigger for when to call it, and naming search_products as where built tools appear implicitly signals the read-then-suggest relationship. There is no explicit "do not use if the tool already exists" exclusion, so it stops short of a full when/when-not statement.

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