Skip to main content
Glama

get_new_since

Query locally persisted Zhihu activity for a specified hour window, optionally filtered by user, without accessing Zhihu. Use it to find recent changes from local records only.

Instructions

Query only locally persisted activity; does not access Zhihu.

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

Input Schema

NameRequiredDescriptionDefault
userNo
hoursNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.2/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It does disclose one genuinely useful trait—this reads only local persistence and performs no Zhihu network access—but says nothing about freshness, staleness, empty results, or what happens when local data is absent.

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

Conciseness3/5

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

It is short and front-loaded, and the no-network fact is worth stating. But the brevity is under-specification rather than economy: the sentence is clipped and omits the subject of "new," so nothing about the retrieval window is conveyed.

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-shape detail is not required, and the tool is simple (two optional params). Still, with 0% parameter coverage and no annotations, the definition should explain the time-window and user-scoping semantics; it does neither, leaving the agent guessing.

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

Parameters1/5

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

Schema coverage is 0% for both parameters, and the description does not mention "user" (nullable, default null) or "hours" (default 24) at all. It does not explain whether hours counts back from now, nor what a null user means—self vs. all users—leaving the core semantics undocumented.

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

Purpose2/5

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

The description states a constraint ("Query only locally persisted activity; does not access Zhihu") but never says what "new" means or what kind of activity is returned. The name implies "items since a time," yet the prose leaves the verb's object vague and does not differentiate it from the sibling get_activities.

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, no stated preconditions (e.g. whether a prior sync must have run), and no alternative named. An agent can only infer "prefer this when you want cached/local data," which is thin for a tool with nine siblings.

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