Skip to main content
Glama

PointBagel

Points portfolio summary

portfolio_summary
Read-only

Summarize the signed-in PointBagel user's own wallet and how well it is working for them: points balances with their estimated value, the wallet roster (every card PointBagel tracks for them, fee or no fee), the cards that carry an annual fee with the fee and when it is due, statement credits about to expire, and rollups of what the wallet costs and how much of its value is being captured across the cards PointBagel can score. Read-only; this user's own cards and programs only, never another person's. Values are estimates. Optional include narrows the answer to one block: balances, fees, credits, cards (the fee timeline with the wallet roster), or optimization (credits at risk).

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

Input Schema

NameRequiredDescriptionDefault
includeNoNarrow the answer to one block. Omit for the whole summary.

Output Schema

NameRequiredDescriptionDefault
asOfYes
dataYes
statusYes
summaryYes
nextActionsNo
userWarningsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already carry readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered; the description adds context the annotations cannot: that values are estimates, that scope is strictly the caller's own wallet, and what each returned block contains. It does not discuss how estimates are derived or what happens when a card cannot be scored, which is why it isn't a 5.

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?

Front-loads the core action and scope, then lists blocks, then closes with scope caveats and the `include` explanation. The middle enumeration is long and dense but every clause identifies a distinct returned section, so little is wasted; only minor tightening would be possible.

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

Completeness5/5

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

For a zero-required-parameter read tool with an output schema, the description covers everything an agent needs: what is returned, whose data (own wallet only), that numbers are estimates, and how to narrow output. Return-value structure is left to the output schema, which is appropriate.

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% with a single enumerated `include` param whose schema already says 'Omit for the whole summary.' The description does add some meaning to two enum values ('cards' = fee timeline with wallet roster; 'optimization' = credits at risk), but the remaining values are essentially restatements of their names, so it sits at baseline with a small lift rather than above it.

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

Purpose5/5

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

States a concrete verb and resource: 'Summarize the signed-in PointBagel user's own wallet and how well it is working for them,' then enumerates the exact blocks returned (balances with estimated value, wallet roster, annual-fee cards, expiring credits, cost/value rollups). This clearly separates it from card-level siblings like card_detail or fee_verdict, which an agent can rule out without reading their schemas.

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?

Gives strong scope guidance: read-only, signed-in user's own cards and programs only, 'never another person's,' and tells the agent that `include` narrows the answer to one block or omits entirely for the whole summary. It stops short of naming an alternative tool for card-level drill-down, so a 4 rather than a 5.

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