Skip to main content
Glama

DataAutomation

get_quote

Price a service with options before ordering. No side effects.

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": {
      "service": "<service>"
    },
    "name": "get_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
optionsNointegration: {"flows":[{"source","destination","data"}]}; training: {"hours"}; fractional-caio-cto: {"hours_per_month"}; ai-we-build-and-run: {"tier": 5000|10000|15000}
serviceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. 'No side effects' is a useful and relevant disclosure that the tool is safe/read-only, but it does not address whether quotes are binding, what permissions are needed, or how invalid options are handled.

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, front-loaded sentences with no filler. The safety note is separated cleanly from the purpose statement, and every phrase earns its place.

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 2-parameter pricing tool with no output schema, the description conveys the core purpose and safety profile. However, it does not describe what a quote response contains (e.g., price amount, currency, line items), which is a meaningful gap when no output schema exists.

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?

The description says only 'with options' and adds no meaning about the required service parameter, service enum values, or per-service option structures. Schema coverage is 50%, and the detailed options description lives entirely in the schema, so the description does not compensate for the remaining gap.

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 states a specific verb and resource: 'Price a service with options.' The phrase 'before ordering' also semantically separates it from create_order, though it does not explicitly name any sibling tool. The purpose is clear and distinguishable in practice.

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?

It gives a clear usage context: call this before ordering to get pricing. It does not enumerate exclusions or name alternatives, but the temporal guidance is sufficient to route an agent away from create_order for a pre-purchase price check.

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