Skip to main content
Glama

get_user_profile

Read-only

Retrieve a Douban user's basic profile information by providing their user ID, enabling account detail lookups when cookies are unavailable.

Instructions

获取某用户的基本信息。无 cookie 时必须传 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": "get_user_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.1
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.0.0-alpha.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered structurally. The description adds the non-obvious auth constraint (uid is mandatory without a cookie), which is real behavioral value, but says nothing about pagination, error behavior when the uid is invalid, or what 'basic information' comprises.

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?

Two short sentences with the purpose front-loaded and the constraint immediately after; no filler or repetition. It is arguably too terse, since more space could have been used to disambiguate the uid format, but nothing present 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?

For a single-parameter, read-only tool with no output schema, the safety profile is handled by annotations and the auth caveat is covered. Still, 'basic information' is undefined and the description provides no sense of what the response contains or how failures behave.

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

Parameters3/5

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

Schema description coverage is 0% and the single uid parameter is typed only as a bare string, so the description has to carry the burden. It clarifies the requiredness condition (mandatory with no cookie) but never says whether uid is a numeric ID, a username, or a site-specific identifier – a gap that matters for correct invocation.

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?

The description uses a concrete verb+resource pair ('获取某用户的基本信息' – fetch a user's basic info) that distinguishes it from siblings such as get_user_collections and get_user_doulist, which return user-specific collections/lists rather than profile data. It does not explicitly name those siblings, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The clause '无 cookie 时必须传 uid' gives a conditional usage cue tied to authentication state, which is genuinely useful context that is not stated anywhere else. However, it offers no guidance on when to choose this tool over the listed user-related siblings, and it never mentions what to do when a cookie IS present.

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