Skip to main content
Glama
ohmstead-mcp

ohmstead-mcp

Official

Who am I

whoami
Read-only

Retrieve the signed-in Ohmstead user, their plan, and the teams and classes they belong to with their role, so you can confirm identity and permissions before editing a design.

Instructions

The signed-in Ohmstead user, plan, and the teams and classes they're in (with their role).

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 observedv0.1.2

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds real value by enumerating the response content (user, plan, teams, classes with role), which matters because no output schema exists. It does not mention behavior when unauthenticated or whether the plan/teams data is scoped or cached, which keeps it below 5.

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 sentence with no filler that front-loads the most important fact (whose identity) before the supplementary details (plan, teams, classes, roles). Nothing could be removed 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, read-only introspection tool with no output schema, the description is nearly complete because it tells the agent exactly what data comes back. The only gap is unstated behavior on failure or missing authentication, which is a minor omission at this complexity level.

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 and the baseline is 4. The description correctly implies no input is required, consistent with the empty schema.

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 names the concrete resource returned: the signed-in user, their plan, and the teams and classes they belong to with roles. That clearly separates it from the sibling tools, which all operate on project/diagram editing. It is a noun phrase rather than an explicit verb ('Returns...'), which keeps it just 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?

There is no explicit when-to-use statement and no alternatives are named, but the usage is strongly implied: call this to learn the current identity, plan, and team/class membership context. Given a zero-parameter self-inspection tool with no near-equivalents among the siblings, the inference burden is small, though the description adds nothing proactive.

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