Skip to main content
Glama

Tomorrow Central: Cloud Cost Sentinel

Who am I here

webops_whoami
Read-onlyIdempotent

Who the token says the caller is in Website Growth Ops: the organization and the permissions it holds here. It changes nothing.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so 'It changes nothing' largely restates structured data. The description does add scope context (organization + permissions attached to the token), but omits behavior beyond that, such as what happens with an invalid or expired token.

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?

Two short sentences, front-loaded with the identity claim, with zero padding. Minor waste in the closing sentence, which duplicates the read-only annotations.

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 zero-parameter, read-only introspection tool with no output schema, the description does the important work of naming what is returned (organization and permissions). With annotations covering the safety profile, little else is needed.

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 there is nothing for the description to disambiguate. Baseline 4 applies.

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 reads as a specific resource statement: 'who the token says the caller is in Website Growth Ops' and names the payload ('the organization and the permissions it holds here'). An agent can tell this is an identity/permissions introspection call. It does not explicitly contrast with the sibling 'whoami', so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: inspect identity and permissions for the current token. There is no explicit when-to-use, no prerequisite (e.g., needed when a call fails with auth errors), and no reference to the sibling 'whoami' to disambiguate the two identity tools.

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