Skip to main content
Glama

Get current Rosuii pricing

get_pricing
Read-onlyIdempotent

Return active plans from Rosuii's central plan catalog in BDT with ISO 8601 billing periods.

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

A3.9/5.0
Behavior4/5

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

Annotations already declare this a read-only, idempotent, closed-world, non-destructive operation, so the safety profile is covered. The description adds real context beyond that: it discloses that only active plans are returned, the currency (BDT), and the format of billing periods (ISO 8601), which shapes how an agent should interpret and present results.

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 sentence that front-loads the core action and packs scope, currency, and period format without any filler. Nothing could be removed without losing information.

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 catalogue read with no output schema, the description carries an appropriate amount of the burden by naming what is returned (active plans), the currency, and the billing-period encoding. It stops short of describing a plan's fields (name, price tiers, included features), which an agent would only discover at call time.

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 parameters, so the baseline is 4 and there is nothing for the description to clarify or compensate for. No parameter meaning is lost.

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 uses a specific verb (Return) against a specific resource (active plans from Rosuii's central plan catalog), and adds scope qualifiers — active only, BDT-denominated, ISO 8601 billing periods. It does not explicitly differentiate itself from siblings like get_feature or get_rosuii, but the pricing resource is distinctive enough that confusion is unlikely.

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 only implied: an agent can infer this is the tool to call for pricing questions, but there is no explicit statement of when to use it, when not to, or what alternative to consider. The 'active plans' qualifier hints that historical or retired plans are out of scope, which is mildly useful routing information.

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