Skip to main content
Glama

get_platform_pricing_and_plans

Retrieve MeetingPoll subscription plans, single-poll passes, organization quorum plans, and free features

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing beyond the subject matter — no indication of whether results are static or live, whether pricing is per-currency or per-region, or what the response looks like. It does not contradict anything, but for a tool with zero annotation coverage the behavioral disclosure is thin.

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 front-loaded sentence naming the resource and its subcategories with no filler. The comma-separated list is efficient, though the enumeration borders on a data dump rather than explaining what the agent should expect back.

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 and no annotations, the description is the only source of information about the return value, and it names the categories covered but says nothing about pricing structure, currency, or completeness of the listing. For a simple zero-parameter read tool this is borderline adequate rather than complete.

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 no parameters, so the baseline of 4 applies; the description adds no parameter meaning because none exists to explain. Nothing misleading is introduced.

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?

States a specific verb ("Retrieve") plus the exact resource categories returned: subscription plans, single-poll passes, organization quorum plans, and free features. This clearly separates it from siblings like get_poll_consensus or check_poll_status, which concern poll state rather than commercial plans, though the description never explicitly names that distinction.

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 by the verb "Retrieve" and the pricing/plan subject matter; there is no explicit when-to-use statement, no prerequisites, and no mention of alternatives or when not to call it. For a zero-parameter lookup tool the implied usage is likely sufficient, but the guidance gap is real.

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