Skip to main content
Glama

AutoTasker Hub — China Social Data API

ithome_news

IT Home (IT之家) tech news feed: titles, summaries, timestamps, comment counts. $0.01 USDC.

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral details on its own. It adds useful cost information ($0.01 USDC) and lists the return fields, but it does not explain freshness, language, auth requirements, rate limits, or pagination behavior. These gaps are significant for a feed-retrieval tool.

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

Conciseness5/5

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

The description is a single, compact sentence that front-loads the source and content type. The price is appended without unnecessary wording, and there is no filler. It is appropriately sized for a simple feed tool.

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 low-complexity tool with one parameter and no output schema, the description covers the source, return fields, and cost. However, it omits the `limit` parameter's behavior and does not clarify feed freshness or language. The definition is usable but leaves gaps that could affect invocation correctness.

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 only input parameter is `limit`, and the schema description coverage is 0%, so the description should compensate by explaining what it controls. The description never mentions `limit` or how many items the feed returns. The parameter name and schema constraints are somewhat self-explanatory, but the description adds no semantic value.

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 names a specific source and resource: the IT Home (IT之家) tech news feed. It also lists the returned fields, so the agent can understand what the tool provides. It does not explicitly differentiate this from sibling news tools, but the source-specific framing is clear.

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?

The description states what the feed contains but gives no guidance on when to use it versus other news or data tools. It also provides no exclusions, prerequisites, or alternative recommendations. The price is mentioned, but that is not usage guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.