Skip to main content
Glama

find_plans

Read-only

Pricing plans across the catalog. An API's pricing tiers. meta says who wrote the file (method), when it was read (provenance_date), who the page prices for (audience), how (pricing_basis), and whether a price is stale. Filter by q / tags / providers; include=["content"] inlines bodies. Use find_artifacts for cross-type search.

Input Schema

NameRequiredDescriptionDefault
qNoFree text over name + description, e.g. "sms".
pageNoPage number, 1-based (default 1).
sortNoOrder: relevance / provider / name, or plan_count (largest first).
tagsNoTag slugs, e.g. ["payments"]. On providers: what the company does (see api_tags).
limitNoResults per page, 1-100 (default 25).
matchNoHow `tags` combine: any (default) or all.any
methodNoWho wrote the file: "searched" (transcribed from the provider's page), "probed" (read live), "generated" (API Evangelist sweep, unverified), "unmarked".
contextNoOptional: one sentence on why you are asking. Never used to rank; read only if a result is wrong.
includeNoPass ["content"] to inline each artifact's body instead of just its URL.
audienceNoWho the pricing page prices for: "developer-api" (API or platform usage), "business-product" (the product the API comes with), "consumer" (a fee schedule), "unclear".
providersNoProvider slugs, e.g. ["stripe"].
pricing_basisNoHow it is priced: "per-call", "per-seat", "ad-valorem", "flat-platform", "tiered-subscription", "usage-other", "negotiated", "free", "none".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / context / description
      Previous value: -"Optional: why you are asking. One sentence — the task you are trying to complete, or what you expect to get back. Never included in the answer and never used to rank; it is read only when a result turns out to be wrong, which is when knowing the intent is what makes the report actionable."New value: +"Optional: one sentence on why you are asking. Never used to rank; read only if a result is wrong."
    • changedInput schema / properties / match / description
      Previous value: -"How multiple `tags` combine: \"any\" (default, at least one) or \"all\" (every tag)."New value: +"How `tags` combine: any (default) or all."
    • changedInput schema / properties / page / description
      Previous value: -"Page number, 1-based (default 1). Use with `limit` to walk a long list."New value: +"Page number, 1-based (default 1)."
    • changedInput schema / properties / providers / description
      Previous value: -"Provider slugs to restrict results to, e.g. [\"stripe\",\"adyen\"]."New value: +"Provider slugs, e.g. [\"stripe\"]."
    • changedInput schema / properties / q / description
      Previous value: -"Free text over name + description."New value: +"Free text over name + description, e.g. \"sms\"."
    • changedInput schema / properties / tags / description
      Previous value: -"Tag slugs. On PROVIDERS this is identity — what the company says it does, from its own apis.yml. A resource or operation term (webhook, saml, order, oai-pmh) will correctly match no provider; use find_apis?tags= for those, or find_providers?api_tags= to reach companies whose APIs merely touch it."New value: +"Tag slugs, e.g. [\"payments\"]. On providers: what the company does (see api_tags)."
  2. Changed5 schema fields changed
    • addedInput schema / properties / include / description
      Added value: +"Pass [\"content\"] to inline each artifact's body instead of just its URL."
    • addedInput schema / properties / limit / description
      Added value: +"Results per page, 1-100 (default 25)."
    • addedInput schema / properties / match / description
      Added value: +"How multiple `tags` combine: \"any\" (default, at least one) or \"all\" (every tag)."
    • addedInput schema / properties / page / description
      Added value: +"Page number, 1-based (default 1). Use with `limit` to walk a long list."
    • addedInput schema / properties / providers / description
      Added value: +"Provider slugs to restrict results to, e.g. [\"stripe\",\"adyen\"]."
  3. Changed3 schema fields changed
    • addedInput schema / properties / audience
      Added value: +{
      +  "description": "Who the pricing page prices for: \"developer-api\" (API or platform usage), \"business-product\" (the product the API comes with), \"consumer\" (a fee schedule), \"unclear\".",
      +  "type": "string"
      +}
    • addedInput schema / properties / method
      Added value: +{
      +  "description": "Who wrote the file: \"searched\" (transcribed from the provider's page), \"probed\" (read live), \"generated\" (API Evangelist sweep, unverified), \"unmarked\".",
      +  "type": "string"
      +}
    • addedInput schema / properties / pricing_basis
      Added value: +{
      +  "description": "How it is priced: \"per-call\", \"per-seat\", \"ad-valorem\", \"flat-platform\", \"tiered-subscription\", \"usage-other\", \"negotiated\", \"free\", \"none\".",
      +  "type": "string"
      +}
  4. Changed1 schema field changed
    • changedInput schema / properties / tags / description
      Previous value: -"Tag slugs. On PROVIDERS this is identity — what the company says it does, from its own apis.yml. A resource or operation term (webhook, saml, order, oai-pmh) will correctly match no provider; use find_apis?tags= for those, or api_tags below."New value: +"Tag slugs. On PROVIDERS this is identity — what the company says it does, from its own apis.yml. A resource or operation term (webhook, saml, order, oai-pmh) will correctly match no provider; use find_apis?tags= for those, or find_providers?api_tags= to reach companies whose APIs merely touch it."
  5. Changed2 schema fields changed
    • changedInput schema / properties / sort / description
      Previous value: -"Order: name, or plan_count (largest first)."New value: +"Order: relevance / provider / name, or plan_count (largest first)."
    • changedInput schema / properties / sort / enum
      Previous value: -[
      -  "name",
      -  "plan_count"
      -]New value: +[
      +  "relevance",
      +  "provider",
      +  "name",
      +  "plan_count"
      +]
  6. Changed1 schema field changed
    • changedInput schema / properties / tags / description
      Previous value: -"Tag slugs."New value: +"Tag slugs. On PROVIDERS this is identity — what the company says it does, from its own apis.yml. A resource or operation term (webhook, saml, order, oai-pmh) will correctly match no provider; use find_apis?tags= for those, or api_tags below."
  7. Changed1 schema field changed
    • addedInput schema / properties / context
      Added value: +{
      +  "description": "Optional: why you are asking. One sentence — the task you are trying to complete, or what you expect to get back. Never included in the answer and never used to rank; it is read only when a result turns out to be wrong, which is when knowing the intent is what makes the report actionable.",
      +  "type": "string"
      +}
  8. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds provenance awareness (method, provenance_date, audience, pricing_basis, staleness) that tells the agent result data may be unverified, which is useful. However much of this overlaps with the schema's own parameter descriptions and it says nothing about pagination or result shape.

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?

Three tight sentences with the purpose front-loaded and no filler. The telegraphic 'meta says...' phrasing is dense but every clause carries information the agent needs; only minor polish is missing.

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 12-parameter, all-optional search tool with annotations covering safety and no output schema, the description covers filtering, inlining behavior, and the sibling alternative. Remaining details (paging, sort order) live in the schema, so little an agent needs is missing.

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%, so the baseline is 3. The description reinforces the main filter axes (q / tags / providers) and include=["content"] behavior but adds no syntax or format detail beyond what the schema already documents for all 12 parameters.

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 names the resource precisely ('Pricing plans across the catalog', 'An API's pricing tiers') and routes the agent to the right sibling for cross-type search ('Use find_artifacts for cross-type search'). It is clear enough to select without opening the schema, though the opening fragment omits an explicit verb and the two-sentence framing is slightly disjointed.

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?

It gives concrete selection guidance: filter by q / tags / providers, add include=["content"] to inline bodies, and defer to find_artifacts when searching across artifact types. No explicit when-not-to-use conditions beyond the cross-type alternative, so it stops short of the top band.

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