Skip to main content
Glama

QConsul LLC

Get pricing and terms

get_pricing_and_terms
Read-onlyIdempotent

Return Standard Hourly and Executive 1:1 Subscription prices and the complete published pricing terms, verbatim from qconsultai.com and structured to mirror the page.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and closed-world, so the safety profile is covered. The description still adds real value by disclosing provenance and fidelity: values come verbatim from qconsultai.com and are structured to mirror the page, which tells the agent to trust the numbers as authoritative published text. It does not mention caching or freshness, which keeps it short of a 5.

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?

A single front-loaded sentence naming the payload first and qualifying its provenance second. No filler, no restatement of the title.

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 parameterless read tool with clear annotations, the description covers what is returned at a high level. The 'structured to mirror the page' phrasing is vague about the actual response shape, which matters somewhat since there is no output schema, but the gap is minor for a simple fetch.

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 the baseline is 4 and the description has no parameter semantics to add. Nothing in the text misdescribes the absence of inputs.

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?

States a specific verb (Return) plus the exact resources (Standard Hourly and Executive 1:1 Subscription prices and the complete published pricing terms). That is clearly distinguishable from sibling operations like check_availability, confirm_booking, or list_services.

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?

The intent is inferable — fetch published pricing and terms — but there is no explicit statement of when to reach for this versus list_services or check_availability, and no prerequisites or exclusions are given. Usage is implied rather than guided.

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