Skip to main content
Glama
Sign In
freispace MCP Server

freispace MCP Server

Official
by freispace
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_current_user

Retrieves the authenticated user's identity, including name, email, and staff record. Resolves personal references to enable context for subsequent queries.

Instructions

Who the calling user is: name, email and their linked staff record. Use it to resolve 'I', 'me' or 'my' to a staff name for other tools.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns name, email, and linked staff record, which is adequate for a simple, read-only identity lookup. No side effects or destructive behaviors are mentioned, but none are expected.

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?

Two concise sentences with no wasted words. The first sentence states what the tool does, and the second sentence provides a practical usage hint.

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?

Given there is no output schema, the description sufficiently covers the return values (name, email, staff record). The tool is simple and the description is complete for its purpose.

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 has no parameters, so the description does not need to add meaning beyond the schema. Baseline score of 4 applies as per instructions for zero-parameter tools.

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 calling user's name, email, and linked staff record. It distinguishes itself from sibling tools like 'get_staffs' (which likely lists all staff) by focusing on the current user's identity.

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 advises using the tool to resolve pronouns like 'I', 'me', or 'my' to a staff name for other tools, providing clear context for when to invoke it. Does not explicitly mention when not to use it, but the purpose is narrow enough.

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