Skip to main content
Glama

List your RFQs

my_rfqs
Read-onlyIdempotent

List your 100 most recent requests and private orders across every status—open, negotiating, agreed, filled, expired or cancelled—including ones hidden from the public board.

Instructions

Your 100 most recent requests and private orders, in every status (open, negotiating, agreed, filled, expired, cancelled). The board (list_open_rfqs) shows only public ones that are open or negotiating. Takes no parameters.

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_rfqs"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
errorNoSet instead when the call failed
itemsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.11.1
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "properties": {
      +    "error": {
      +      "additionalProperties": {},
      +      "description": "Set instead when the call failed",
      +      "properties": {
      +        "code": {
      +          "type": "string"
      +        },
      +        "is_retryable": {
      +          "type": "boolean"
      +        },
      +        "message": {
      +          "type": "string"
      +        },
      +        "recovery_hint": {
      +          "type": "string"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "items": {
      +      "items": {
      +        "additionalProperties": {},
      +        "properties": {
      +          "askPrice": {
      +            "description": "Total ask; null if none",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "baseAmount": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "rfqId": {
      +            "description": "Request id",
      +            "type": "string"
      +          },
      +          "status": {
      +            "type": "string"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Addedv0.10.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare that the tool is read-only, idempotent, non-destructive, and open-world, so the basic safety profile is covered. The description adds useful behavior beyond the annotations: it caps results at the 100 most recent records and confirms that all statuses and private orders are included. It does not describe pagination or return format, but an output schema exists and annotations already carry the safety signals.

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 primary scope, then immediately contrasts list_open_rfqs, then closes with the no-parameter note. Every clause earns its place, and there is no filler or repetition.

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 zero-parameter list tool with an output schema and rich annotations, the description supplies everything the agent needs: the result cap, status coverage, privacy scope, and explicit differentiation from the sibling board tool. Nothing material is missing.

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?

The tool has zero parameters, so there is no parameter semantics burden; baseline is 4. The description reinforces this by stating 'Takes no parameters,' which prevents an agent from searching for missing inputs.

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 states a specific resource and scope: 'Your 100 most recent requests and private orders, in every status (open, negotiating, agreed, filled, expired, cancelled).' It clearly distinguishes this from list_open_rfqs by contrasting private/all-status RFQs with the public open/negotiating board. An agent can identify exactly what this tool returns without opening the schema.

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?

The description explicitly names the alternative tool, list_open_rfqs, and explains the condition that selects it: 'The board (list_open_rfqs) shows only public ones that are open or negotiating.' This gives the agent a clear decision rule between this tool and its most similar sibling.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.