Skip to main content
Glama

Get services and pricing

get_pricing_and_services
Read-onlyIdempotent

What National Digital builds and supports, and what each kind of project typically costs, in AUD. Includes the Product Support retainer for ongoing engineering on production platforms, including platforms built by other teams, and the standard hourly rate card for work outside a retainer. Ranges are indicative and are built from the Product Support retainer rates; they are not quotes. Returns an empty list when no pricing has been published, rather than an estimate.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 safety (readOnly, idempotent, non-destructive, closed-world), so the description adds genuine behavior beyond them: currency (AUD), the provenance of the ranges (derived from Product Support retainer rates), retainer coverage including platforms built by other teams, an hourly rate card for out-of-retainer work, and the empty-list-on-no-data behavior. The one gap is it does not say what the returned records look like or whether results are grouped by service.

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?

It is front-loaded with what the tool returns and stays dense with useful facts (currency, retainer, rate card, empty-list fallback). There is mild repetition between 'they are not quotes' and 'rather than an estimate', and the single long paragraph could break the pricing caveat into its own sentence, but nothing is wasted outright.

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?

With no output schema, the description carries the burden of describing returns, and it only covers one edge case (empty list) without outlining the shape of a normal response — whether it lists services and ranges separately, or how the retainer and hourly card are represented. For a zero-param read tool this is adequate but leaves the agent guessing at result structure.

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?

There are zero input parameters, so the baseline is 4 and there is nothing for the description to disambiguate. It correctly avoids inventing parameter guidance for a parameterless call.

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 states a specific verb-and-resource pair: it returns what the company builds/supports plus typical project costs in AUD. It is clearly a services-and-rate-card lookup rather than a calculator or form submission. It does not name the closest sibling (estimate_project) explicitly, so differentiation is implied by 'ranges are indicative... not quotes' rather than stated.

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: consult this for indicative pricing and service scope, and understand the numbers are not quotes. However, it never says when to prefer this over estimate_project for a real figure, nor does it state any preconditions. The agent must infer the routing decision from the sibling name alone.

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