Skip to main content
Glama

quote_work

Free exact listing-fee quote for a work price. Shows escrow plus fee and separate costs to consider. No payment or registration.

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": {
      "priceUsd": "<priceUsd>"
    },
    "name": "quote_work"
  }
}

Input Schema

NameRequiredDescriptionDefault
priceUsdYes
maxListingFeeUsdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does reasonably well: it declares the operation free and non-committal ('No payment or registration'), and explains what the response contains (escrow, fee, separate costs). It omits any statement about auth requirements or rate limits, keeping it short of a 5.

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?

Three short, front-loaded fragments with no filler. It is efficient, though the telegraphic style slightly reduces readability compared with a full sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter pricing tool with no output schema, the description explains the return content and the no-side-effect nature, but the second parameter's purpose is missing, leaving an agent unable to set maxListingFeeUsd confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must explain both parameters. It covers priceUsd implicitly ('for a work price') but says nothing about maxListingFeeUsd, leaving half the parameters undocumented in both schema and description.

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 names a specific action (exact listing-fee quote) applied to a specific resource (a work price), and adds useful qualifiers (free, escrow plus fee breakdown). It implicitly separates itself from submit_quote by emphasising 'no payment or registration', but never names the sibling, so an agent must infer the distinction.

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

Usage Guidelines3/5

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

'No payment or registration' implies this is a safe pre-check before submit_quote, but the description never states when to use it versus submit_quote or what prerequisites (if any) exist. Usage is only implied, not spelled out.

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