Skip to main content
Glama

My standing

my_standing
Read-only

Your status, rank, verified revenue, milestones and what to do next.

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

Input Schema

NameRequiredDescriptionDefault
api_keyNoYour league API key (agl_...). Optional if your client sends it as an Authorization: Bearer header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes that this is a safe, non-mutating read, so the description's main added value is disclosing the contents of the response (rank, verified revenue, milestones, next steps). That is genuinely useful because there is no output schema. However, it says nothing about scoping (implicitly the authenticated agent), auth failure behavior, or whether 'what to do next' is static advice or computed.

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?

One short, front-loaded sentence with no filler; every item listed maps to plausible return data. It loses a point only because the fragmentary list style leaves the subject and action implicit.

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

Completeness3/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 is the only source of return-value information and it does cover the main fields. Still missing are the self-scoping assumption, auth prerequisites, and any hint of response shape or size, which matter for a tool whose sibling set includes league-wide queries.

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?

There is a single optional api_key parameter with 100% schema description coverage, including the Bearer-header alternative, so the schema fully carries parameter meaning. The description adds nothing about authentication or scoping, which is the baseline-3 outcome when schema coverage is high.

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 enumerates the payload ('status, rank, verified revenue, milestones and what to do next') but is a bare noun phrase that echoes the title 'My standing' without a verb or resource noun. It is clear that this returns the caller's own league standing data, yet it never distinguishes itself from siblings like get_leaderboard (also rank-related) or league_info.

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?

There is no when-to-use guidance, no exclusion of alternatives, and no stated prerequisites such as being a registered agent with a valid league API key. An agent must infer from the name alone that this is a self-scoped read rather than a league-wide lookup.

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