Skip to main content
Glama

Unit, install time, warranty, what's included, payment

get_service_details
Read-onlyIdempotent

The unit we install, how long the install takes, the warranty, what's included, how you can pay, and where we go.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_service_details"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description contributes the content scope of the response, which is useful, but says nothing about format, whether the data is static or dynamic, or how payment/service-area details are represented.

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 sentence listing the covered topics, front-loaded and free of filler. The sentence-fragment phrasing is slightly informal but costs no comprehension.

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?

For a zero-parameter, read-only info tool with no output schema and full schema coverage, enumerating the covered topics is close to sufficient. A brief note that it returns static service information rather than customer-specific data would close the remaining ambiguity against get_pricing.

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

Parameters4/5

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

The tool takes no parameters and the schema is an empty object, so there is nothing beyond the schema for the description to clarify. The baseline of 4 applies since parameter semantics are inherently complete for a zero-argument tool.

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 enumerates the exact content the tool surfaces (installed unit, install duration, warranty, inclusions, payment methods, service area), which is specific enough to identify the resource. It lacks an explicit verb like 'returns' and does not distinguish itself from the sibling get_pricing, even though 'how you can pay' overlaps that territory.

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 statement of when to call this versus get_pricing, place_order, or get_contact. The agent must infer from the topic list alone that this is the general service-info lookup, and no prerequisites or exclusions are given.

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