Skip to main content
Glama

Read the cancellation questions

get_membership
Read-onlyIdempotent

The questions asked about a cancellation the member made, with their ids. Actions: cancellation_questions. Call with action "help" for each action's fields.

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": {
      "action": "<action>"
    },
    "name": "get_membership"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
paramsNoFields for the action. Call with action "help" to list each action's fields.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "cancellation_questions",
      -  "preview_upgrade",
      -  "upgrade_link",
      -  "upgrade_trial_link",
      -  "preview_term",
      -  "change_term_link",
      -  "preview_plan_change",
      -  "change_plan_link",
      -  "switch_trial_plan_link",
      -  "help"
      -]New value: +[
      +  "cancellation_questions",
      +  "help"
      +]
  2. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact — that a "help" action enumerates each action's fields — but says nothing about what the response contains beyond "ids" or whether the list is paginated or scoped.

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?

Two short sentences with no padding, and the help mechanism is stated after the purpose. The first sentence is grammatically awkward ("The questions asked about a cancellation the member made, with their ids"), which slightly blunts the front-loading but wastes no words.

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?

This is a small, closed-world, read-only tool with two parameters, and the description covers the action name and the self-documenting help path. Still, an agent must call "help" to learn what to pass in params, and nothing is said about the shape of the returned question records, so it is adequate but not self-sufficient.

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 50%: the action enum values and the params object are typed in the schema, and the params description already points at "help." The description reinforces the help mechanism and mentions that results carry ids, but it adds no syntax, format, or field-level meaning for the nested params object beyond what the schema states.

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

Purpose3/5

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

The description identifies the resource as "the questions asked about a cancellation the member made, with their ids" and names the single action (cancellation_questions), so the intent is inferable. However, it never uses a clear verb like "retrieve" or "list," and the value does not explain how this relates to the tool name get_membership or to the sibling manage_membership, leaving ambiguity about scope.

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?

The only guidance is "Call with action \"help\" for each action's fields," which explains parameter discovery rather than when to use this tool. There is no statement of when to choose this over manage_membership, get_answers, or other read tools, and no prerequisites or exclusions are given.

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.