Skip to main content
Glama

get_more_tools

Report that the user's request needs a capability this server does not have. Records the report for the server's developers; it does not return or add tools.

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

Input Schema

NameRequiredDescriptionDefault
contextYes
conversation_idNoThe conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.

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?

Adds real value beyond the annotations: it discloses the write side effect ('records the report for the server's developers'), which is consistent with readOnlyHint=false, and explicitly negates the expected behavior of fetching/adding tools. It does not cover whether repeated or duplicate reports are acceptable, whether the call has any user-visible effect, or what the agent should tell the user afterwards.

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 short sentences, front-loaded with the action and immediately followed by the clarifying side-effect/limitation. Nothing is redundant, and the disclaimer about not returning tools is placed where it matters most.

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 simple two-parameter reporting tool with annotations and no output schema, the description covers purpose, side effect, and the key negative expectation. The remaining gap is guidance on 'context' contents and on repetition, which is minor but not trivial for a report-submission tool.

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?

The conversation_id parameter is documented in the schema itself, but the required 'context' field has no schema description, leaving only the implication that it should describe the missing capability. The description does not state what to put in 'context' (e.g., the user's request text vs. a capability label) or any format expectations, so the 50% coverage gap is only partly compensated.

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 concrete verb and object — report that a requested capability is missing — which is far more specific than the tool name suggests. It also pre-empts the name's misleading implication by stating it does not return or add tools. It stops short of contrasting itself with the sibling feedback/report channels, so sibling differentiation is only partial.

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?

Gives a clear triggering condition: the user's request needs a capability this server does not have. It offers no exclusions or pointers to alternatives (e.g., reportBuckyFeedback or submitBuckyFeedback for ordinary feedback), so the agent must infer when another reporting path is more appropriate.

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.