Skip to main content
Glama

get_current_user

Retrieves the full profile of the authenticated MantisBT user via the /users/me endpoint, helping you identify the active account and access its details.

Instructions

Returns the full profile of the authenticated user (/users/me) in MantisBT.

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 observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description must carry the behavior burden. It does disclose a few things: "Returns" signals a read-only operation, "authenticated user" implies an auth requirement, and the /users/me endpoint gives the underlying API call. It does not state what happens when the caller is unauthenticated, what fields the "full profile" contains, or whether any sensitive data is exposed.

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?

A single, front-loaded sentence with no filler. The resource, the return semantics ("full profile"), and the endpoint are all packed in without redundancy.

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 zero-parameter read tool this is close to sufficient, and no output schema exists so return values arguably need explaining. However, "full profile" is the only hint about the response, and there is no mention of auth failure behavior — both are gaps an agent would want filled given the absence of annotations and output schema.

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?

This tool takes zero parameters, so there is no parameter semantics to explain and the schema is trivially complete. Baseline 4 applies; nothing in the description is needed or missing on this dimension.

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 verb and resource: "Returns the full profile of the authenticated user (/users/me) in MantisBT." An agent can immediately tell this is an identity/profile lookup, distinct from the issue-, project-, and config-oriented siblings. It stops short of explicitly naming a sibling to contrast with, so it lands at 4 rather than 5.

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?

There is no when-to-use guidance at all: no mention of when the current-user profile is needed, no prerequisites, no alternatives (e.g. versus get_project for ownership info). The only implied usage signal is the word "authenticated," which hints at an identity-confirmation scenario.

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