Skip to main content
Glama

estimate_automation

Read-only

Deterministic automation sketch for a task. Pricing is always the same picture: start task SEK 2,900 excl. VAT, ongoing run SEK 490 excl. VAT, invoice via Bokio after approved delivery. No monthly price bands, no randomness. Same input → same JSON. Not a binding quote. Free First Task (0 SEK) is the optional free plan before ordering.

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": {
      "task_description": "<task_description>"
    },
    "name": "estimate_automation"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNo
hourly_rate_sekNo
task_descriptionYes
consultant_hours_per_monthNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Beyond the readOnly/closed-world annotations, the description adds real behavioral context: the call is deterministic (same input, same JSON), contains no randomness or monthly price bands, and is explicitly not a binding quote. It also discloses the invoicing path (Bokio after approved delivery), which the annotations do not cover.

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?

Purpose and price picture are front-loaded, and the disclaimers arrive in a sensible order. Minor redundancy between 'no randomness' and 'same input → same JSON', but nothing is materially wasteful.

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?

With no output schema the description usefully describes what comes back (fixed price structure, JSON, non-binding), which is the main complexity of this tool. However, four parameters with zero schema coverage are left entirely unexplained, leaving a real gap for an agent deciding what to pass in.

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 four parameters, so the description carries the full burden and fails to explain any of them — task_description, hourly_rate_sek, consultant_hours_per_month, or the en/sv language enum. The pricing prose describes output, not the inputs that drive it.

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 identifies a concrete output (a deterministic automation sketch with a fixed price picture: start task SEK 2,900, ongoing SEK 490) and states it is a non-binding quote, so an agent can tell what it produces. It stops short of naming which sibling (get_pricing_model, get_offer, start_proposal) it should be preferred over.

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?

Usage is only implied: 'Not a binding quote' and the note that Free First Task is the optional free plan 'before ordering' situate it in a pre-sales flow. There is no explicit when-to-use, when-not-to-use, or named alternative among the many pricing/proposal siblings.

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