Skip to main content
Glama

Who am I

get_me
Read-onlyIdempotent

Check a key: whose it is, the account's balance, the key's scopes, mode and monthly allowance with what it has committed this month, the rate limits, and every operation this key cannot call with the reason and the remedy. Call this first with a new key. (GET /api/v1/me)

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_me"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered structurally. The description adds useful context about the richness of the response (including denied operations and their remedies), but since there is no output schema, it does not commit to the actual shape or naming of those fields, leaving the agent to discover the format by calling.

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-loaded with the core action and then a dense but purposeful enumeration; the trailing endpoint reference is compact. The middle clause ('monthly allowance with what it has committed this month') is slightly tangled and would read faster as a list, but no sentence is filler.

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 carries the burden of explaining returns, and it does so thoroughly by category. It stops short of describing response structure or field names, which an agent will still need to inspect on first call, but for a zero-parameter introspection tool it is close to complete.

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 the baseline is 4; there is nothing for the description to disambiguate. It correctly implies no inputs are needed by saying to call it with just a key.

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?

The description gives a specific verb plus resource ('Check a key') and then enumerates exactly what the check reveals: identity, balance, scopes, mode, monthly allowance vs. committed usage, rate limits, and forbidden operations with reasons. That enumeration makes it unmistakable versus siblings like get_results or list_calls, which return operational data rather than key introspection.

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?

It gives an explicit sequencing rule — 'Call this first with a new key' — which is real when-to-use guidance tied to a concrete situation. It doesn't name alternatives or state when not to call it, but for a zero-parameter diagnostic tool there is little ambiguity to resolve.

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.