Skip to main content
Glama

IRM Consulting & Advisory

Get published pricing

get_pricing
Read-onlyIdempotent

Published IRM pricing: the monthly subscription tiers (hours per month, stage, summary) and, if service_id is given, that service's starting price. All prices are USD per month and are starting prices.

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
service_idNoOptional service id to get its starting price.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world behavior. The description adds value beyond them by disclosing units (USD per month) and a crucial caveat that all prices are starting prices, which an agent would otherwise misreport as exact quotes.

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 well-formed sentence that front-loads the resource and appends the conditional behavior. It is dense but every clause (tier fields, conditional price, units, starting-price caveat) earns its place.

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?

With no output schema, the description takes on the job of describing the return payload and does so at a useful level (tier fields plus a conditional price field). Minor gaps remain around whether tiers are always returned and how the price is formatted, but nothing blocking.

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

Parameters3/5

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

Schema coverage is 100% and the enum already enumerates valid service ids, so the schema carries most of the burden. The description does clarify the effect of supplying versus omitting service_id (includes that service's starting price), but adds little about format or fallback behavior.

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?

States a specific resource and scope: published IRM pricing, naming the monthly subscription tiers (hours per month, stage, summary) and the optional per-service starting price. It is clearly distinguishable from siblings like get_service or list_services, though it doesn't name them.

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 implied by the phrase 'published ... pricing' and the conditional 'if service_id is given', which tells the agent when the extra data appears. However, there is no explicit when-to-use guidance relative to pricing-adjacent siblings such as get_service or check_availability.

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