Skip to main content
Glama

user_profile

Fetch public profile details for a specific Zhihu user by token, enabling read-only lookup of account information.

Instructions

Read public profile information for one Zhihu user.

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": {
      "token": "<token>"
    },
    "name": "user_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.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 disclosure burden. It adds one genuinely useful behavioral fact: only public profile fields are returned, which bounds the data exposure. It says nothing about token/auth requirements, rate limits, or failure modes, and the presence of an output schema covers the return shape.

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?

One front-loaded sentence with no wasted words. Its terseness is also its weakness, because the missing detail is precisely what would fill the other gaps, so it is not a perfect 5.

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?

This is a simple read-only lookup with one parameter and an output schema, so the description does not need to explain return values. What is missing is what 'token' means and what 'public' excludes, which matters for correct invocation. The definition is minimally viable for a tool of this complexity.

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?

The single parameter 'token' has 0% schema description coverage, and the schema gives it only a generic title, so nothing explains it. The phrase 'for one Zhihu user' weakly implies the token identifies the target user rather than being an auth credential, but this ambiguity is never resolved. With only one parameter and a simple shape, the gap is real but narrow, so 2 rather than 1.

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: "Read public profile information for one Zhihu user." That clearly distinguishes it from sibling retrievers such as get_activities or get_answer_detail, which return other resource types. It stops short of a 5 only because it does not explicitly name a competing alternative.

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 statement of when to use this tool versus alternatives, and no prerequisites are mentioned. 'Public' hints that no extra auth scope is needed, but the agent gets no explicit trigger or exclusion.

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