Skip to main content
Glama

Get More Tools

getMoreTools
Idempotent

Tell the Clera team about a capability you needed that none of these tools offer. It only records your description; it does not call, install or suggest any other tool or connector.

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": "getMoreTools"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextYesWhat you were trying to do and which capability was missing.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.9/5.0
Behavior3/5

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

Annotations declare destructiveHint=false, idempotentHint=true, and openWorldHint=true, and the description usefully confirms this is a write-only recording action that sends nothing further to the caller. It does not say what happens afterward (whether the team replies, when, or whether repeated submissions are deduplicated despite the idempotent hint), which is the key behavioral unknown for an agent deciding whether to call it.

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, zero filler: the first states the action, the second front-loads the most likely agent misconception (expecting it to return tools). Nothing could be removed without losing information an agent needs.

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 one-parameter, annotation-covered tool with no output schema, the description covers what it does, what it does not do, and when to use it. The only real gap is the post-submission lifecycle — silence versus a reply — which leaves an agent unsure of what it should do after calling.

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?

The single 'context' parameter has 100% schema description coverage, so the baseline is high, and the description reinforces the expected content by framing it as the capability that was missing rather than, say, feedback on existing tools. It adds the constraint that the missing capability must not be among the offered tools, which the schema alone does not state.

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 states concretely that the tool records a missing-capability request for the Clera team, countering the misleading name 'getMoreTools' by explicitly saying it does not call, install, or suggest tools. It is specific about the resource (a capability description) but uses prose rather than a crisp verb+resource phrasing, and the sibling list contains nothing comparable to differentiate against.

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?

It gives a clear trigger — use this when a capability you needed is offered by none of the available tools — and an explicit exclusion that it will not fetch or recommend connectors. It stops short of naming any alternative route (e.g., a support channel or a different tool) for the same goal, so guidance is clear but not complete.

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