Paired Plus by Cotlet

Get gift card balances in Paired Plus

paired_plus_get_gift_card_balances

Read-onlyIdempotent

Get gift card balances in the user's own Paired Plus account from ChatGPT, Claude or any AI agent. Returns how to do it in Paired Plus step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Paired Plus Cloud Browser. Paired Plus's official API: The ProSolutions Paired host publishes API help, but no self-serve API key or onboarding guide was found.

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": "paired_plus_get_gift_card_balances"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Beyond annotations confirming read-only, non-destructive, idempotent, closed-world behavior, the description adds that the tool only returns instructions and performs no action itself. It also discloses the API limitation about no self-serve API key or onboarding guide, which is useful operational context.

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?

The core workflow is front-loaded, but the second sentence is long and includes an API-help tangent that is only loosely relevant to invoking the tool. The description could be tightened without losing the essential guidance.

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 zero-parameter, no-output-schema guidance tool, the description explains what is returned in general terms, that no direct action occurs, and which tools to use next. It is reasonably complete, though it could more explicitly state the expected format or scope of the returned step-by-step instructions.

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

Parameters4/5

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

There are zero parameters, so the baseline is 4. The description does not need to explain parameter semantics, and no parameters are undocumented.

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 states a specific resource and clarifies that the tool returns step-by-step instructions rather than directly fetching balances. It also names the complementary cotlet_browser_* tools, though the name 'Get gift card balances' could initially mislead an agent into expecting an actual data retrieval.

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 clearly says the tool returns procedural steps and opens nothing by itself, and that the agent should then use cotlet_browser_* tools in the user's Paired Plus Cloud Browser to execute the action. It does not explicitly say when to prefer sibling gift-card tools such as redeem or sell, but the workflow guidance is otherwise clear.

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

All Paired Plus by Cotlet tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?