Skip to main content
Glama

Posted countertop pricing

get_pricing
Read-onlyIdempotent

ATX Granite King's posted prices, what they include, service area and contact details.

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_pricing"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 openWorldHint=false, so the safety profile is fully covered elsewhere. What the description adds is content scope: it returns posted prices with their inclusions plus contact details, framing this as static published reference data rather than a calculation. It does not describe the response shape, but no output schema exists and the tool is a zero-parameter read, lowering the burden.

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 short clause with no filler; the resource owner and content types are front-loaded. The comma-list of offerings is slightly unstructured, but every element maps to real returned content, so nothing is wasted.

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, closed-world lookup with no output schema, the description tells the agent enough about what comes back (prices, inclusions, service area, contact details) to decide to call it. The only real gap is routing guidance against the quote and service-area siblings, which the description does not attempt.

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, so the baseline is 4 and there is no parameter meaning for the description to clarify. It correctly avoids inventing inputs and instead spends its words on what the content covers.

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 names the specific resource (ATX Granite King's posted prices) and enumerates the content: what prices include, service area, and contact details. It is a noun phrase rather than a verb+resource, and 'what they include' is vague, but an agent can tell this returns published reference pricing rather than a computed quote.

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?

No when-to-use or when-not-to-use guidance is given, and no alternative is named. This matters because several siblings overlap directly — check_service_area covers the service-area content claimed here, and get_quote/generate_quote cover pricing — so the agent is left to infer whether this is the right source for a given pricing question.

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