Skip to main content
Glama

Principal Reputation for Agents

check_standing

Pre-acceptance standing check $0.02 (trial/fleet apply)

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

Input Schema

NameRequiredDescriptionDefault
amountNo
work_classNo
principal_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses a $0.02 cost, but it does not state whether the check is read-only, what permissions are required, what happens on failure, or what result the caller receives.

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 description is a single compact fragment with the core purpose placed first, so it is not bloated. However, it is so compressed that the parenthetical and cost placement feel cryptic rather than structured.

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

Completeness2/5

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

For a tool with three undocumented parameters, no annotations, and no output schema, the description is insufficiently complete. It provides only a purpose fragment and a cost note, leaving the agent without the context needed to invoke the tool correctly.

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

Parameters1/5

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

All three parameters (amount, work_class, principal_id) have 0% schema description coverage, and the description does not explain any of them. With no compensation for the schema gap, an agent cannot infer how to set these parameters.

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 names a specific action, "standing check," with the qualifier "pre-acceptance," so it is more than a tautology. However, "standing" remains undefined, and it does not clearly distinguish this tool from the sibling get_standing, so the purpose is only minimally clear.

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 parenthetical "(trial/fleet apply)" hints at a usage context but does not explicitly say when to use this tool instead of get_standing or any other sibling. There are no exclusions, prerequisites, or alternative-routing instructions.

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