Skip to main content
Glama

Get pricing facts

get_pricing_facts
Read-onlyIdempotent

Use this when the user asks what one AI tool costs or what its free tier includes. Returns verified pricing facts first; catalog text only when no verified price exists, labeled catalog_only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "platform": "<platform>"
    },
    "name": "get_pricing_facts"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformYesA Launchpad HQ platform slug or name.

Output Schema

NameRequiredDescriptionDefault
plansYes
platformYes
free_tierYes
lifecycleYes
data_as_ofYes
api_pricingYes
attributionYes
usage_limitsYes
verificationYes
catalog_pricing_textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedOutput schema / properties / platform / properties / freshness_note
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / platform / properties / resolution
      Added value: +{
      +  "anyOf": [
      +    {
      +      "enum": [
      +        "compact",
      +        "alias",
      +        "spelling"
      +      ],
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedOutput schema / properties / platform / properties / resolved_from
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / platform / properties / stale
      Added value: +{
      +  "type": "boolean"
      +}
  2. Changed1 schema field changed
    • addedOutput schema / properties / platform / properties / tasks
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context beyond them: result provenance ordering (verified facts first, catalog text only as a fallback) and the "catalog_only" label an agent can key on when reasoning about reliability.

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?

Two sentences, no filler. The usage trigger is front-loaded and the return-behavior sentence follows immediately, which is the correct ordering for an agent deciding whether to call.

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?

With an output schema present, return value shape needn't be explained, and the description still adds the provenance semantics that the schema cannot express. What is absent is routing against siblings (compare, find_free_alternatives) when the user's question spans more than one tool, which slightly under-equips an agent at a decision boundary.

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 description coverage is 100% and the single `platform` parameter is documented as a slug or name, so the schema does the heavy lifting. The description reinforces the singular scope ("one AI tool"), but adds no format, resolution, or ambiguity-handling detail beyond what the schema states; baseline 3 applies.

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?

"Get pricing facts" plus the scoping phrase "what one AI tool costs or what its free tier includes" gives a concrete verb and resource (pricing + free-tier data for a single tool). The word "one" implicitly separates it from compare and search_tools, but no sibling is named outright, so the differentiation is inferential rather than explicit.

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

Usage Guidelines4/5

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

The first sentence is an explicit use trigger: "Use this when the user asks what one AI tool costs or what its free tier includes." It is missing explicit when-not guidance (e.g., "for multiple tools use compare"), so the agent must infer that multi-tool comparison belongs to the sibling.

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.