Skip to main content
Glama
bruhsb
by bruhsb

paperclip_get_current_user

Read-only

Retrieve the authenticated board user and session identity to verify which human operator is active before performing board actions.

Instructions

⚠ Board-only: Return the authenticated board user and their session identity.

Args:

  • response_format: 'markdown' | 'json' (optional) — Output format (default: markdown)

Returns: { userId: string|null, user: { id, email, ... }|null }. userId is null when no board session is active.

Examples:

  • Use when: verifying which human operator is authenticated before performing board actions

  • Don't use when: you need the current agent's identity — use paperclip_get_me instead

Error Handling:

  • 401: authentication failed → check that a board (human) API key is being used

  • 404: no active session → the board token may have expired

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
response_formatYesOutput format: 'markdown' (default, human-readable) or 'json' (structured)markdown
Behavior5/5

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

Annotations already declare readOnlyHint=true, and the description adds important behavioral context: it is board-only, requires a board API key, and includes error handling details for 401 and 404 cases. No contradictions with annotations.

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?

The description is well-structured with sections (Args, Returns, Examples, Error Handling), front-loads a warning icon for visibility, and every sentence adds essential information without redundancy.

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

Completeness5/5

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

For a simple read-only tool with one parameter and no output schema, the description fully covers return type, error handling, and usage context. It is sufficiently complete for an AI agent to invoke correctly.

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?

Schema coverage is 100% with a well-described parameter, but the description adds the clarification that response_format is optional (despite schema marking it required) and reiterates the default. This adds value beyond schema, but the improvement is marginal.

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?

The description clearly states the tool returns the authenticated board user and session identity, with a specific verb 'Return' and resource 'board user'. It directly distinguishes itself from the sibling tool paperclip_get_me by specifying board user vs agent identity.

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

Usage Guidelines5/5

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

The description provides explicit 'Use when' and 'Don't use when' instructions, including a named alternative (paperclip_get_me), giving clear guidance on when to select this tool over siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bruhsb/paperclip-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server