Skip to main content
Glama

PlanComply SANS 10400 Building Compliance

get_credit_pricing

Retrieve official Plan Comply Studio Credit packages (R149 Single, R590 5-Pack, R1,490 15-Pack), 2-Pass Pre-Council Sketch + .DXF CAD Schedule export entitlements, and checkout 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_credit_pricing"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It makes clear this is a static lookup of published catalogue data (prices, entitlements, checkout details), which implies a safe read, but it never states read-only status, whether prices are fixed or region-dependent, or how fresh the data is.

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 with the core action front-loaded and no filler. The enumerated prices lean toward describing return values rather than purpose, which adds length without adding invocation guidance.

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, no-output-schema tool this is reasonably complete: the agent knows what data comes back and roughly in what shape. The one loose end is "checkout details," which is not defined — an agent cannot tell whether this means payment flow, currency, or purchase links.

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, so there is nothing for the description to disambiguate; the baseline applies. Listing concrete package tiers actually helps the agent recognize that no filtering inputs are needed.

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?

Uses a specific verb ("Retrieve") tied to a specific resource (Plan Comply Studio credit packages, export entitlements, checkout details). The sibling tools all concern compliance rules and calculations, so there is no realistic confusion to differentiate against, but the description itself does not name any alternative.

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 content — an agent would call this when it needs credit pricing or package/entitlement information — but there is no explicit statement of when to use it, when not to, or what to call instead if only compliance rules are needed.

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