Skip to main content
Glama

Read rebate balance

evuun_rebate
Read-onlyIdempotent

Read the signed-in person's EVUUN rebate balance. Changes nothing.

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

Input Schema

NameRequiredDescriptionDefault
actionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false. The description adds the useful auth scope that the balance belongs to the "signed-in person," but "Changes nothing" largely restates the annotation safety profile without additional details such as freshness or permissions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences are front-loaded with the core action and scope. There is no unnecessary wording, and the read-only implication is stated immediately.

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 simple read-only tool with rich annotations, no required parameters, and no output schema, the description gives enough context to invoke it correctly. Its only material omission is explaining the optional `action` parameter.

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

Parameters2/5

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

The schema has one optional `action` parameter with the enum value "view" and 0% description coverage. The description never mentions `action`, so it does not compensate for the missing schema documentation, though the single-value enum is fairly self-explanatory in the schema itself.

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 verb and resource: "Read the signed-in person's EVUUN rebate balance." This clearly distinguishes a balance-viewing operation from sibling names like evuun_rebate_use, though it does not explicitly name the alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase "Changes nothing" implies this is the safe read-only option for viewing a balance, contrasted with a spend/use sibling. However, it does not explicitly say when to use this instead of evuun_rebate_use or any other alternative.

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