Skip to main content
Glama

me_get

The account this API key belongs to, the key in use, its scopes, and the credit balance available to spend.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description bears the full behavioral burden, and it does disclose the returned content — which is valuable since there is no output schema. However, it never states that the operation is read-only/side-effect free, what happens with an invalid or expired key, or how the balance is formatted. For a zero-argument introspection call the risk is low, but the disclosure is incomplete rather than thorough.

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?

A single compact sentence with zero filler, front-loading the most important item (the account) and enumerating the rest in a natural reading order. Nothing could be cut without losing information.

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 no-parameter tool with no output schema, the description must carry the return-value story, and it does by listing the four returned items. What is missing is only secondary: confirmation of read-only semantics and error behavior for an invalid key. Given the tool's simplicity, the definition 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 of 4 applies. Nothing in the description conflicts with the empty schema, and no parameter meaning needs to be supplied.

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 enumerates exactly what the tool surfaces: the owning account, the API key in use, its scopes, and the credit balance. That is enough for an agent to recognize it as a self-introspection 'who am I' call, distinct from the resource-specific siblings like document_get or run_get. It is phrased as a noun fragment with no explicit verb ('Returns...'), which slightly blurs whether it fetches or describes, but the intent is recoverable.

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 mention that it takes no arguments, and no stated alternative or precondition. The listed fields hint at use cases (checking scopes before a call, checking credits before run_start), but the agent must infer all of that. No exclusions or routing advice are provided.

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