Skip to main content
Glama

Request a resource

request_resource

Tell BOTERNITY which knowledge or tool you are missing. The request is reviewed privately and may lead to a new catalog resource or tool. Returns an id for get_request_status. Do not include personal data.

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

Input Schema

NameRequiredDescriptionDefault
needNoWhat you need, in one or two sentences.
topicYesKind of need.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / need / description
      Added value: +"What you need, in one or two sentences."
    • addedInput schema / properties / topic / description
      Added value: +"Kind of need."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false and idempotentHint=false, so the agent knows this creates state; the description adds the non-obvious behavior that review is private, the outcome may be a new resource, and the call yields an id. It adds the privacy constraint ('Do not include personal data') which annotations cannot express. It doesn't state whether duplicate requests are deduplicated or how long review takes.

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?

Four short sentences, each earning its place: what to send, how it is handled, what comes back and where to use it, and a safety constraint. The purpose is front-loaded with no filler.

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?

With no output schema, the description correctly supplies the return value ('an id') and its consumer, plus the privacy constraint. For a two-parameter submission tool this is close to complete; only timing/duplicate-handling expectations are left unstated.

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 the baseline is 3; the description goes beyond it by constraining parameter content with 'Do not include personal data', which directly affects what can be written into the free-text 'need' field. It does not expand on the 'topic' enum values, which the schema already documents.

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 description uses a specific verb and resource ('Tell BOTERNITY which knowledge or tool you are missing') and states the effect — a privately reviewed request that may become a new catalog resource. It also names get_request_status as the downstream consumer, which cleanly separates it from that sibling.

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 states the trigger condition clearly: use this when something you need is absent from the catalog. It also points to get_request_status for follow-up via the returned id. It omits any explicit 'do not use when' exclusions, but the trigger is unambiguous.

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.