Skip to main content
Glama

Get request details

get_request
Read-onlyIdempotent

Get one request with its goal, must-have and nice-to-have constraints, interest count and all proposals. USE WHEN evaluating whether software satisfies a request, before proposing a solution, or before the requester records a verdict. NO side effects; public. interest_count is the requester plus supporters, not purchase intent. A proposal with status 'proposed' has not been accepted.

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": {
      "request_id": "<request_id>"
    },
    "name": "get_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idYesRequest ID (req_...).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already declare read-only, idempotent, non-destructive, and closed-world behavior, and the description reinforces this with 'NO side effects; public.' It also adds useful semantics beyond annotations, clarifying that interest_count includes the requester plus supporters and is not purchase intent, and that status 'proposed' means not accepted.

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?

The description is front-loaded with the core purpose, followed by usage conditions and then field-specific clarifications. Every sentence adds actionable information with no redundant wording.

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 simple one-parameter read tool with no output schema, the description is complete enough: it explains what is returned, when to use it, safety properties, and the most ambiguous field semantics. Nothing essential for correct invocation appears 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 the single request_id parameter is already documented as a req_... ID. The description does not add syntax, format, or validation meaning beyond the input schema, so the baseline score 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?

The description states a specific verb and resource: get one request, and enumerates returned content including goal, constraints, interest count, and proposals. It is clear but does not explicitly distinguish itself from sibling search_requests or get_history beyond the singular 'one request' scope.

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 explicit USE WHEN conditions: evaluating whether software satisfies a request, before proposing a solution, and before the requester records a verdict. It does not name alternative tools or state when not to use this one, so it falls short of full when/when-not/alternatives guidance.

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