Skip to main content
Glama
Sign In
mindin

mindin

by gronare
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

whoami

Reports the authenticated connection identity and whether write access is allowed as JSON, so clients can verify permissions before changing vault notes.

Instructions

CHEAP — who this connection signs in as and whether it may write. Answers JSON.

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

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.15.1

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations provided, the description must carry the full behavioral burden. It discloses the two things returned (identity and write capability) and that the result is JSON, and 'CHEAP' signals low cost. It says nothing about auth/permission failure behavior, side effects, or whether identity can be absent, which matters for an auth-probing tool.

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?

Extremely tight and front-loaded: cost hint first, then what is answered, then the format. 'Answers JSON' is largely redundant given an output schema exists, so one clause is spent on information already carried structurally, but nothing else is wasted.

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?

A small zero-parameter identity probe with an output schema, so return-value detail is unnecessary. The description tells the agent what questions it answers and roughly what it costs, which is sufficient; only the meaning of 'may write' and failure/auth modes remain unstated.

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. No schema burden is left unmet.

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?

States a specific outcome: the identity this connection authenticates as plus whether it may write. That is concrete verb/resource information an agent can act on, and no sibling tool (close, lint, set_status, etc.) overlaps with it, though the phrasing 'who this connection signs in as' is slightly roundabout versus simply naming the operation.

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?

The leading 'CHEAP' tag implies 'prefer this when you just need to confirm identity/capability rather than doing a real read', which is useful implicit guidance. However it never states when to call it, when not to, or names any alternative diagnostic tool, so usage is only implied.

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

Deploy Server

Other Tools