Skip to main content
Glama
Sign In
Jotify Moment MCP Server

Jotify Moment MCP Server

by daocatt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

jotify_get_profile

Verify an API key and retrieve the authenticated user's profile details, including nickname, slug, and role. Use this tool to confirm credentials and access account information.

Instructions

验证 API 密钥并获取当前登录用户的个人资料（昵称、Slug、角色等）

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden. It discloses that API key verification is part of the operation and specifies what data is returned (nickname, slug, role). While it doesn't mention read-only status or potential side effects, the 'get' verb and profile context imply a safe read operation.

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 a single, concise sentence that front-loads the purpose. It wastes no words and includes useful details about fields returned.

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?

For a tool with no parameters, no output schema, and no annotations, the description is adequately complete. It covers purpose, auth verification, and the content of the response. It could be considered complete enough given the tool's simplicity.

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?

There are zero parameters, so the baseline is 4. The description does not need to explain parameter semantics, and it correctly avoids mentioning any parameters.

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 verb '获取' (get) and the resource '当前登录用户的个人资料' (current logged-in user's profile), and lists specific fields (nickname, Slug, role). This distinguishes it from sibling tools which handle media uploads and post creation.

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 implies usage context by indicating it verifies API key and fetches profile, which is a distinct operation from the sibling tools. It does not explicitly state when not to use it, but the context is clear enough given the tool's purpose.

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