Skip to main content
Glama

subscription_promotional_offers_prices_get_to_many_relationship

Retrieves the prices associated with a subscription promotional offer by its ID, enabling you to manage offer pricing.

Instructions

GET /v1/subscriptionPromotionalOffers/{id}/relationships/prices (GET /v1/subscriptionPromotionalOffers/{id}/relationships/prices)

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": {
      "id": "<id>"
    },
    "name": "subscription_promotional_offers_prices_get_to_many_relationship"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
limitNomaximum resources per page

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

C2.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 disclosure burden, and it supplies almost none. The 'GET' verb implies a read, but there is nothing about pagination behavior (implied by the limit parameter), authentication requirements, or what the relationship payload contains.

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 short line, so there is no padding to trim, but the line is pure duplication of the name and path, meaning no sentence earns its place by adding information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read endpoint with no annotations and no output schema, the description should at least clarify the relationship fetch semantics and pagination via limit. It leaves the agent without the context needed to choose this tool over its _related twin.

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 both parameters (id, limit) are documented in the schema, so the baseline of 3 applies. The description adds no syntax, format, or usage nuance beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The text is a verbatim restatement of the tool name and URL path, so it adds no meaning beyond what the identifier already conveys. It does not explain what a prices relationship for a subscription promotional offer is, nor distinguish it from the almost identically named subscription_promotional_offers_prices_get_to_many_related sibling.

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, no prerequisites, and no mention of the relationship-vs-related alternative that sits right next to it in the tool list. The agent must infer usage entirely from the endpoint shape.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools