Skip to main content
Glama

AutoTasker Hub — China Social Data API

comment_for_post

Fetch fake comments attached to a PostID (JSONPlaceholder). Demo data. $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": "comment_for_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
postIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden and does disclose two non-obvious traits: the data is fake (JSONPlaceholder demo) and the call costs $0.01 USDC. That is genuine value beyond the schema. It still omits return shape, pagination/ordering behavior, and what happens when postId does not exist, which matters for a billable call.

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?

Four short fragments, front-loaded with the operation and resource, and every clause (source, data is fake, cost) adds actionable information. It is terse to the point of being telegraphic, but there is no filler to cut.

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 two-parameter read with no annotations and no output schema, the definition covers what the tool returns conceptually and flags that it is paid demo data. Given the absence of an output schema, it should say more about the comment objects returned and about the undocumented limit parameter to be fully self-sufficient.

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. It explains postId only implicitly (comments "attached to" it) and never mentions limit at all — neither its default of 5, its maximum of 20, nor whether limit applies per post or overall. Half the parameters remain unexplained across both sources.

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?

"Fetch fake comments attached to a PostID" gives a specific verb (fetch) and resource (comments scoped by postId), which is enough for an agent to know exactly what this returns. It also names the backing source (JSONPlaceholder) and the data nature (fake/demo). It stops short of differentiating from any sibling, but none of the listed siblings overlap in behavior.

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 explicit when-to-use or when-not-to-use guidance; the agent must infer that this is only appropriate for demo/mock purposes from the fragment "Demo data." No alternatives, prerequisites, or constraints on calling frequency are stated.

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.