Skip to main content
Glama

A11y Probe

get_pricing

Read-only

Prices in USD, rate and daily limits, and links to the terms and privacy notice. Automated checks find roughly 57% of WCAG issues. Free.

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

C2.7/5.0
Behavior2/5

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

The readOnlyHint annotation already establishes this is a safe read. Beyond that the description adds essentially nothing about the tool's behavior, and 'rate and daily limits' is ambiguous — it reads as plan/pricing content rather than disclosure of the tool's own rate limiting, so an agent could misread it. The 57% WCAG statistic is irrelevant to behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text is a set of sentence fragments with no clear front-loaded statement of what the tool does, and it wastes a full sentence on an unrelated WCAG 57% statistic. The word 'Free' is dangling with no context.

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 zero-parameter, annotation-covered, no-output-schema tool the burden is modest, and the description does roughly cover the returned fields (prices, limits, legal links). However, the absence of a clear statement of purpose and the irrelevant marketing sentence leave the agent working to assemble the picture.

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 zero parameters at 100% schema coverage, so there is no parameter semantics to add. Baseline 4 applies; the description cannot be faulted for missing parameter detail.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description enumerates the content the tool returns (USD prices, rate and daily limits, links to terms and privacy notice), which hints at a pricing-lookup tool, but it never states a verb or explicitly says 'returns pricing information.' The trailing sentence about automated checks finding 57% of WCAG issues is marketing copy that muddies rather than clarifies purpose.

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 guidance on when to call this tool versus alternatives, and no mention of siblings like scan_page, scan_site, or report. The agent is left to infer that this is a static informational lookup, and the 'Free' fragment provides no usage context.

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.