Skip to main content
Glama

My requests

my_requests
Read-onlyIdempotent

Deprecated, use requests_list and request_get (real status, categories, files). Quote and service requests you submitted while signed in, newest first: reference, type, status, product, date and your message (wrapped as data). Guest submissions are not listed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "my_requests"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows (1-20).
cursorNoValue of next_cursor from the previous page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: newest-first ordering, the exact fields surfaced, the exclusion of guest submissions, and that the user's message is 'wrapped as data' (a notable prompt-injection safeguard). It does not state pagination behavior, though the cursor param implies 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?

The deprecation warning is front-loaded in the first clause, followed by scope, ordering, returned fields, and caveats in a compact run. Every clause carries distinct information; there is no filler or repetition of the schema.

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?

With no output schema, the description usefully enumerates the returned fields, states ordering, and flags an exclusion that would otherwise look like missing data. Combined with the deprecation routing and full schema coverage for the two parameters, an agent has everything needed to decide whether to call it and how to interpret results.

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 coverage is 100%, with limit (1-20, default 10) and cursor fully documented in the schema, so the baseline of 3 applies. The description's 'newest first' hints at ordering semantics but adds nothing about limit or cursor usage beyond what the schema already states.

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?

States the resource precisely ('quote and service requests you submitted while signed in'), the ordering ('newest first'), and the fields returned (reference, type, status, product, date, message). It also opens with a deprecation pointer to requests_list and request_get, so an agent immediately knows what this tool is and what supersedes it.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says the tool is deprecated and names the two replacements, including the concrete reason to prefer them ('real status, categories, files'). It also gives a scope exclusion ('Guest submissions are not listed'), so an agent knows when results will be incomplete rather than assuming an empty answer is authoritative.

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