Skip to main content
Glama

Who am I

flypost_whoami
Read-only

Current Flypost user, active project, and plan summary.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/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 openWorldHint=false, so the safety profile is covered. What the description adds beyond that is the only disclosure of return content (user, project, plan), which matters since no output schema exists, but it says nothing about cost, freshness, or what happens when no project is active.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with zero padding, but it is an incomplete noun phrase rather than a structured statement, and terseness here shades into under-specification rather than efficiency. Adding a verb would cost nothing and add clarity.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a no-parameter read tool with annotations and no output schema, the definition covers roughly what is returned and its non-destructive nature, which is the minimum an agent needs to call it safely. It is still silent on when to reach for it and what the response looks like absent an active project or plan.

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 clarify beyond the schema's empty object. Baseline 4 applies; the sentence does at least confirm the tool is a pure read of ambient session state.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The fragment names three specific things the tool returns (current user, active project, plan summary), which lets an agent infer this is an identity/context lookup and distinguish it from the creation-oriented siblings. However there is no verb ('Get'/'Returns'), so the statement reads as a label rather than a stated purpose, leaving it just at minimum viability.

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?

The description gives no when-to-use guidance, no prerequisites, and no mention of any alternative. An agent must guess that this is the cheap first call to establish session context before doing project work, which is a plausible but unstated inference.

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.