Skip to main content
Glama

My proformas

my_proformas
Read-onlyIdempotent

Deprecated, use quotation_list and quotation_get. Your own proforma invoices (price quotes), newest first: number, status, validity, total, currency and lines. Prices of lines quoted on request are null.

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

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.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real context beyond that: results are newest-first, and line prices quoted on request come back as null, which prevents misreading nulls as errors.

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?

Two sentences, deprecation notice front-loaded, then a compact enumeration of returned fields and the null-price caveat. No wasted wording.

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?

No output schema exists, but the description enumerates the returned fields and the null-price edge case, and the schema covers both parameters. Adequate for a simple two-parameter list tool, though it could note that pagination follows the cursor field.

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%, with limit (1-20, default 10) and cursor fully documented in the schema. The description adds nothing about pagination or parameter meaning, so the baseline 3 applies.

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 resource and scope ("Your own proforma invoices (price quotes)") plus the ordering and the fields returned (number, status, validity, total, currency, lines). This clearly separates it from quotation_list/quotation_get, which the description names as replacements.

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?

Explicitly marks the tool as deprecated and routes the agent to quotation_list and quotation_get, which is strong when-to-use guidance. It does not say which of the two replacements covers which case, but the exclusion of this tool is unambiguous.

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