Skip to main content
Glama

get_activities

Retrieve recent public Zhihu activities for a specified user, with an optional count and opt-in persistence to save results only when requested.

Instructions

Read recent public activity. Persistence is off unless explicitly requested.

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": {
      "user": "<user>"
    },
    "name": "get_activities"
  }
}

Input Schema

NameRequiredDescriptionDefault
userYes
countNo
persistNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It notes that persistence is off unless requested, but that merely restates the schema default (persist=false); it says nothing about what "public" excludes, permission or login requirements, rate limits, or pagination behavior for count.

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, front-loaded sentences with no filler; the persistence caveat is placed after the primary purpose, which is the right order. The sparseness is a coverage problem rather than a verbosity problem.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 values need not be described, but for a three-parameter tool with no annotations and 0% schema coverage the definition leaves too much unexplained — notably user scoping and the effect of persist=true — for an agent to call it confidently.

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, and it largely does not: it never explains whose activity `user` refers to (self vs. arbitrary user), what `count` bounds are, or when setting `persist` to true is appropriate or what it causes.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a verb+resource ("Read recent public activity"), so the general operation is clear, but "activity" is underspecified and nothing distinguishes it from siblings like get_new_since, get_comments, or search_content, which could all plausibly return activity-like data.

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 when-to-use guidance and no named alternative; an agent cannot tell from this text whether to call this or get_new_since/search_content. The only conditional statement concerns persistence, not tool selection.

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