Skip to main content
Glama

Who am I

standcast_whoami
Read-onlyIdempotent

Identify the authenticated GitHub account and its organizations for Standcast so users can verify the correct login before drafting standups.

Instructions

Returns the GitHub login signed in to Standcast and the organizations.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
orgsYes
loginYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed-world scope, so the safety profile is fully covered without the description. The description adds only that the identity is a GitHub login tied to Standcast plus its organizations; it says nothing about authentication requirements, failure behavior, or caching.

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 front-loaded sentence naming the return content with no filler, hedging, or repetition. Every clause earns its place.

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 inputs, complete annotations, and an output schema documenting the return shape, the description covers what the agent needs in order to call it correctly. The only missing piece is a note on identity prerequisites or error behavior when unauthenticated, which is minor for a parameterless read.

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 and there is no parameter semantics for the description to compensate for. Nothing in the schema is left ambiguous by the absence of parameter prose.

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 states a specific verb and resource: it returns the signed-in GitHub login plus the organizations for the current Standcast session. That is enough for an agent to distinguish it from siblings such as standcast_get_digest or standcast_list_teams, though it never explicitly contrasts itself with them.

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: an agent can infer this is the tool for establishing 'who am I' / which orgs are in scope before other calls. There is no explicit when-to-use, when-not-to-use, or prerequisite statement, and no mention of what happens when no user is signed in.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.