freshservice-mcp

Overview Schema Source Related Servers Discussions Admin

get_me

Retrieve the profile of the currently authenticated user in Freshservice, including email and agent details, using OAuth or API key authentication.

Instructions

Return the identity of the currently authenticated user.

When an OAuth token is present (forwarded by ContextForge), the tool decodes the JWT payload to extract the user's email, then queries the Freshservice agents API to return the full agent profile. Falls back to GET /api/v2/agents/me when using API key authentication (local dev / stdio).

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_me"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Aug 9, 2026

TDQS

A4.7/5.0

Behavior5/5

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

With no annotations, the description fully carries the behavioral disclosure burden. It transparently explains the internal flow: JWT decoding, querying the Freshservice agents API, and falling back to a different endpoint for API key auth. This gives the agent a clear picture of what happens and what authentication requirements exist.

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 concise and well-structured. The first sentence immediately states the primary purpose, and the second sentence provides necessary detail about authentication paths. Every sentence adds value without unnecessary filler.

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?

Given the tool's low complexity, empty input schema, and presence of an output schema, the description fully covers what the tool does and how it behaves in different authentication contexts. No critical information is missing for an agent to invoke and understand the tool.

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 zero parameters, so schema coverage is trivially complete. The description adds context about authentication behavior, but no parameter semantics are needed. A baseline score of 4 is appropriate for a parameterless tool.

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's purpose: 'Return the identity of the currently authenticated user.' It uses a specific verb and resource, and the tool name 'get_me' is reinforced. This distinguishes it from the sibling 'manage_*' tools, which focus on mutations.

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?

The description provides clear context on when each authentication path applies (OAuth token vs. API key fallback), which helps an agent understand expected execution environments. While it doesn't explicitly contrast with alternative tools, no similar sibling exists, so this guidance is sufficient for a simple identity lookup.

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