Skip to main content
Glama

ADS Beast

whoami

Read-only

Report the name of the API key in use, the ADS Beast organization it belongs to, the scopes it carries and, in one line, whether it is read-only or can propose changes. The scope list is what a 403 from any other tool in this server refers to: a key without read:leads reaches no lead tool, whatever else it holds.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety is covered structurally. The description adds real value beyond that by enumerating the returned fields (key name, organization, scopes, read-only/propose mode) in the absence of an output schema, and by explaining the diagnostic meaning of scopes. It does not cover latency, caching, or whether the result reflects live key state.

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, front-loaded with what is reported, then a second sentence that earns its place by tying scopes to 403 diagnosis. No filler or repetition of the title.

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

Completeness5/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 carry the return-value burden, and it does by listing the four things reported. For a zero-parameter, read-only introspection tool, nothing an agent needs to invoke it correctly is missing.

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 and the schema is an empty object, so there is no parameter meaning for the description to add. Baseline for a 0-param tool is 4, and nothing here misleads about inputs.

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 names a specific verb (report) and concrete resources: the API key name, its ADS Beast organization, its scopes, and a read-only vs. propose-changes flag. That is distinct from every sibling tool listed (analytics, audit, campaign tools), so an agent can identify it as the identity/permission-introspection tool without opening the schema.

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 a clear use context by explaining that the scope list is what a 403 from any other tool refers to, which tells the agent to call it when troubleshooting permission failures. It stops short of an explicit "call this before/after X" directive or any when-not guidance, so it is clear but not fully prescriptive.

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.