Skip to main content
Glama
Sign In

US compliance and books health

by com.medianfi
OverviewDiscussionsAdmin

Get pricing

get_pricing
Read-onlyIdempotent

Median's published pricing: the flat monthly fee by revenue band under $1M in annual revenue, custom pricing above $1M, what is included, and add-on pricing for tax, R&D credits, and sales tax.

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

A4.3/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, closed-world operation. The description adds useful scope context by specifying that it covers published pricing details, revenue-band pricing, and add-ons, rather than just restating the tool name.

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

Conciseness5/5

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

It is a single dense sentence that front-loads the core purpose and enumerates the relevant pricing dimensions without unnecessary filler. Every clause contributes to understanding what pricing information is available.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 pricing tool with no output schema, the description provides enough detail about what the response will cover: band-based fees, custom pricing thresholds, inclusions, and add-on pricing. No further behavioral or input detail is needed.

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 has zero parameters, so there is no parameter semantics to explain. The description correctly focuses on the returned pricing scope rather than inventing input details.

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

Purpose5/5

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

The description names a specific resource and enumerates the exact pricing content covered: revenue bands under $1M, custom pricing above $1M, inclusions, and add-on pricing. This is clearly distinguishable from the sibling tools, none of which are pricing-focused.

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 topic: an agent should call this when a user asks about Median's pricing. However, the description does not explicitly state when to use this versus alternatives such as get_company_overview, list_services, or explain_obligation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All US compliance and books health toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources