Skip to main content
Glama
merit-aktiva-mcp

merit-aktiva-mcp

by lauri911

Merit Get Sales Offer

merit_get_sales_offer
Read-only

Retrieves a complete sales offer by ID, including the quote, sales order, or prepayment invoice header, rows, and status.

Instructions

One sales offer (quote, sales order or prepayment invoice) in full: header, rows, status.

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": {
      "id": "<id>"
    },
    "name": "merit_get_sales_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesSIHId from merit_list_sales_offers

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that the single record is returned 'in full' with header, rows, and status, which is modest value beyond the annotations and the output schema, but says nothing about authorization needs or error behavior for a missing id.

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 front-loaded sentence with the resource and scope first and the content breakdown after; no filler. It borders on terse, since the parenthetical is doing a lot of disambiguation work in very few words.

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 one fully documented parameter, annotations covering the safety profile, and an output schema defining return structure, the description only needs to clarify what a sales offer is and that it returns one complete record, which it does. The remaining gap is routing guidance versus the list and invoice-retrieval siblings.

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% and the single id parameter is already documented as an SIHId from merit_list_sales_offers. The description adds no format, sourcing, or fallback detail beyond the schema, so the baseline 3 applies.

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?

States a specific retrieval action on a specific resource and disambiguates the term 'sales offer' into quote, sales order, or prepayment invoice, which an agent cannot infer from the name alone. It also signals scope ('one') versus the sibling list tool, though it never names that sibling.

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?

'One sales offer ... in full' implies a detail lookup after a listing call, and the schema ties the id to merit_list_sales_offers, but the description itself gives no explicit when-to-use or when-not-to-use guidance against merit_list_sales_offers or merit_get_sales_invoice.

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