Skip to main content
Glama
Sign In
hedgedoc-mcp

hedgedoc-mcp

by mrsunglasses-experiments
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

hedgedoc_whoami

Read-only

Verify the current session and return the logged-in user's profile. Call before write operations to confirm authentication or identify the active account.

Instructions

Verify the current session is valid and return the logged-in user's profile.

Returns JSON with user info (status, id, name, photo). Call this to confirm the server is correctly authenticated before attempting write operations, or to identify which account is active.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.0
    • addedInput schema / title
      Added value: +"hedgedoc_whoamiArguments"
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely new context: the call doubles as an authentication health check before writes, and it returns JSON with status/id/name/photo. It stops short of describing failure behavior for an invalid session.

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?

Front-loads the core action in the first sentence, then adds return shape and usage guidance. Every sentence earns its place, though the 'confirm the server is correctly authenticated' phrasing overlaps slightly with 'Verify the current session is valid' in the opening line.

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 output schema present, the description does the right thing by summarizing the return payload (status, id, name, photo), which an agent needs to consume the result. It is nearly complete for a zero-parameter read tool; only the invalid-session/error path is left 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 per the calibration baseline a 4 applies. The description correctly implies no inputs are needed by framing this as a session check, and there are no parameter semantics to specify.

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

Purpose5/5

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

States a specific verb+resource pair ('Verify the current session', 'return the logged-in user's profile') and is clearly distinct from the note-oriented siblings (create_note, read_note, note_info, list_history). An agent can identify this as the authentication/identity probe without opening the schema.

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

Usage Guidelines4/5

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

Explicitly names two trigger conditions: 'confirm the server is correctly authenticated before attempting write operations' and 'identify which account is active'. That is strong when-to-use guidance, though it does not state any when-not condition or name an alternative tool for the same goal, which is why it falls short of a 5.

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