Skip to main content
Glama

List my requests (manufacturers)

list_my_requests
Read-onlyIdempotent

For a manufacturer's agent (needs the supplier token): the open quote requests your company was matched to, newest first, with readiness, whether you answered, your quote and unread buyer messages.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
supplier_tokenNoOnly if your client cannot send the Authorization: Bearer header
include_answeredNoDefault true

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, and the description adds real value beyond them: the supplier-token auth requirement, newest-first ordering, and the shape of each returned row (readiness, answered flag, your quote, unread buyer messages). Minor tension: it says the call 'needs the supplier token' while the schema presents supplier_token as a fallback only when no Authorization header is available.

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?

A single dense sentence with the audience and auth constraint front-loaded before the payload description; nothing is wasted, though the parenthetical auth note and trailing comma-list make it slightly harder to scan than a tighter two-clause phrasing.

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 and only three params, the description does the heavy lifting by enumerating returned row contents and stating the auth path. It stops short of covering pagination/limit behavior, which is the one meaningful gap for a list endpoint.

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 67% and the description explains none of the three parameters directly. It implies a default 'open' filter but never clarifies limit or the include_answered default (which the schema says is true), leaving a small mismatch between the stated 'open requests' scope and the default behavior.

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 a specific verb (list), resource (open quote requests your company was matched to), audience (manufacturer's agent), and ordering (newest first). This cleanly separates it from singleton siblings like get_request and thread-oriented tools like get_rfq_thread.

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?

Names the precondition that selects this tool — you are acting as a manufacturer's agent — which implicitly excludes buyer-side use, and states the auth requirement. It does not, however, point at alternatives such as get_request for a single request or explicitly say when not to use it.

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