Skip to main content
Glama
Sign In
coolapk-mcp-pro

coolapk-mcp-pro

by yufeng-liang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

coolapk_user_profile

Fetch a Coolapk user's profile by UID to review account details and community information for read-only user lookup.

Instructions

查看酷安用户资料。

Args: uid: 用户UID

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "uid": "<uid>"
    },
    "name": "coolapk_user_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it says nothing about read-only nature, authentication requirements, rate limits, or whether a failing uid returns an error or empty result. This leaves the agent without key behavioral context beyond the plain 'view' implication.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loads the action before the args block. It is terse to the point of under-specification, but nothing is wasted.

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?

An output schema exists, so return-value details need not appear here, and the single required parameter is listed. However, the absence of usage guidance and any behavioral notes leaves the definition minimally adequate for a one-parameter read tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, but 'uid: 用户UID' only restates the parameter name. It does not explain where a uid comes from, whether it accepts usernames, or format expectations.

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+resource: '查看酷安用户资料' (view Coolapk user profile). An agent can tell this fetches profile data, but the description does not distinguish it from adjacent siblings such as coolapk_author or coolapk_user_feeds.

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 guidance on when to use this tool versus coolapk_author, coolapk_author_digest, or coolapk_user_feeds, and no prerequisites or exclusions are stated. The agent must infer usage purely from the tool name.

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