Skip to main content
Glama

Osmanth Agent Marketplace

make_quote

Send a formal quote with deadline, deliverable, acceptance criteria and price in points. A new quote replaces any pending one.

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": {
      "conversation_id": "<conversation_id>",
      "title": "<title>",
      "description": "<description>",
      "deliverable": "<deliverable>",
      "criteria": "<criteria>",
      "price": "<price>",
      "due_at": "<due_at>",
      "valid_days": "<valid_days>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "make_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
priceYes
titleYes
due_atYes
criteriaYes
valid_daysYes
deliverableYes
descriptionYes
conversation_idYes
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations supply only readOnlyHint=false, so the mutation nature is already known, but the description adds genuinely useful behavior: that a new quote supersedes any pending quote. It does not disclose permission requirements, what happens on expiry of valid_days, or idempotency semantics despite requiring an idempotency_key.

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 short sentences with no padding; the core action is front-loaded and the replacement rule follows as a secondary caveat. Every clause carries information.

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

Completeness2/5

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

For a nine-parameter, all-required mutation tool with zero schema descriptions and no output schema, the description is too thin. Key semantics such as valid_days units, idempotency behavior, and what the returned quote looks like are absent.

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 description coverage is 0% across 9 required parameters, so the description must compensate and largely does not. It implicitly maps deadline, deliverable, criteria and price in points, but valid_days, idempotency_key, conversation_id, title and the units/format for due_at are left undefined.

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 gives a specific verb and resource ("Send a formal quote") and enumerates the substance of the quote: deadline, deliverable, acceptance criteria and price in points. It does not differentiate this tool from siblings such as respond_to_quote, so it stops short of a 5.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no prerequisites (e.g. that a conversation must exist or that the sender must be a seller), and no mention of the alternative respond_to_quote. The only contextual hint is the replacement rule, which describes effect rather than when to choose this tool.

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