Skip to main content
Glama

Request an object

request_object

Ask obbjects to add an object it doesn't have yet. Use after search_objects finds no good match. Requests are reviewed and the most wanted objects are photographed or sourced first. Nothing is returned now; search again later.

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": {
      "description": "<description>"
    },
    "name": "request_object"
  }
}

Input Schema

NameRequiredDescriptionDefault
useNoOptional: what it is for, e.g. 'slide about office supplies'
descriptionYesThe object, as specific as useful, e.g. 'red office stapler, side view'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false; the description adds genuinely new context that nothing is returned now, that requests are human-reviewed and demand-prioritized, and that the agent must search again later. That async, no-immediate-result behavior is the key thing annotations cannot express. It does not address duplicate requests or whether the call can fail on invalid input, which matters given idempotentHint=false.

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?

Three short sentences, front-loaded with the action and followed by the trigger condition and the expected outcome; no filler. The typo 'obbjects' and slightly awkward 'Ask obbjects to add' cost it a point on polish.

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 two-parameter, non-destructive submission tool with no output schema, the description covers purpose, trigger, and the fact that no result is returned immediately, which is what an agent most needs. It could go further on request deduplication and on what makes a request actionable, but nothing essential is missing.

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?

Schema description coverage is 100% and both properties carry their own examples, so the schema does the heavy lifting. The description adds no parameter-level detail such as how specific 'description' should be or what 'use' changes downstream. Baseline 3 applies.

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 resource: asking the service to add an object it lacks. It also implicitly distinguishes itself from search_objects by naming it as the precursor, though the typo 'obbjects' slightly muddies the actor. An agent can tell this is a write-a-request tool, not a retrieval tool.

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 an explicit trigger: 'Use after search_objects finds no good match,' which is exactly the routing decision an agent needs. It does not state any exclusions (e.g., don't request objects that likely exist under a different name) or how specific the request must be to be accepted, so it stops short of a 5.

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