Skip to main content
Glama

PolarJay prices

get_pricing
Read-onlyIdempotent

Published plans in US dollars excluding tax, the queries each includes, the free trial, the done-for-you service and the free scanner, with the pricing page URL.

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
localeNoAnswer language: en (English).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / locale / enum
      Previous value: -[
      -  "en"
      -]New value: +[
      +  "es",
      +  "en"
      +]
  2. Changed2 schema fields changed
    • changedInput schema / properties / locale / description
      Previous value: -"Answer language: es (Spanish) or en (English). Defaults to en."New value: +"Answer language: en (English)."
    • changedInput schema / properties / locale / enum
      Previous value: -[
      -  "es",
      -  "en"
      -]New value: +[
      +  "en"
      +]
  3. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and a closed world, so the safety profile is covered. The description adds genuinely useful interpretation context beyond that: prices are in US dollars and exclude tax, and the response bundles the trial, service offering, scanner, and page URL — details an agent cannot derive from annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded sentence with no filler, but it is a comma-separated fragment with an awkward, grammatically broken clause ('the queries each includes'). The density is appropriate; the phrasing costs readability.

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 simple, read-only, single-parameter lookup with no output schema, the enumerated content effectively substitutes for a return description. Nothing essential to correct invocation is missing, aside from the unmentioned locale parameter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, with the single locale enum fully documented in the schema, so the baseline is 3. The description never mentions the language parameter, leaving a small gap, but the schema carries the burden adequately.

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 enumerates exactly what the tool returns: published plans, USD prices excluding tax, per-plan query allowances, free trial, done-for-you service, free scanner, and the pricing page URL. That makes the resource unambiguous and clearly distinct from siblings like get_product or list_faq, though it is a noun-phrase content list rather than an explicit verb+resource statement.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance and no mention of the sibling tools (get_page, get_product, how_to_start) as alternatives. An agent must infer on its own that this is the pricing-specific lookup rather than a general page/product fetch.

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