Skip to main content
Glama
tremendous-mcp

tremendous-mcp

by Bryan21B

Tremendous account

get_account
Read-only

Retrieve the connected Tremendous organization, environment (SANDBOX or PRODUCTION), and funding-source balances to identify which account you are acting on before rewards or order management.

Instructions

Show the connected Tremendous organization, the environment (SANDBOX or PRODUCTION) and the funding sources with their balances. Call this first to know which account you act on.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavioral context: the call surfaces the connected organization, reveals whether the agent is in SANDBOX or PRODUCTION, and returns funding-source balances — the environment disclosure is especially valuable since acting on the wrong environment would be consequential.

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 sentences, both earning their place: the first enumerates the returned resources, the second gives the calling rule. The returned payload is front-loaded before the instruction, which is the right order for an agent deciding whether to call.

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?

With no output schema, the description must state what comes back, and it does so concretely — organization, environment, funding sources with balances. It is complete for a parameterless read call, with only minor gaps such as whether funding sources are paginated or limited.

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?

The tool takes zero parameters, so there is no parameter meaning to convey and the baseline of 4 applies. Nothing in the description misleads about inputs.

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?

"Show the connected Tremendous organization, the environment (SANDBOX or PRODUCTION) and the funding sources with their balances" names a specific verb and three concrete resources, so the agent knows exactly what comes back. It does not explicitly distinguish itself from the look-alike sibling list_funding_sources, which is the only remaining ambiguity.

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?

"Call this first to know which account you act on" gives an explicit ordering rule and the reason for it, which is real when-to-use guidance. It stops short of naming when-not-to-use or which sibling supersedes it for funding-source-only queries.

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