Skip to main content
Glama

AutoTasker Hub — China Social Data API

pinyin_convert

Chinese text to pinyin with tone marks. Local compute. $0.01 USDC.

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": {
      "text": "<text>"
    },
    "name": "pinyin_convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
toneNo

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, the description carries the full burden, and it does add two useful behavioral facts: the computation is local (no external service) and it costs $0.01 USDC. However, it says nothing about error behavior for non-Chinese input, output shape, or how the tone flag changes results, which leaves real gaps.

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?

Three terse fragments, front-loaded with the core purpose and zero padding. It is telegraphic rather than illegible, though the clipped style leaves little room for the detail that is missing elsewhere.

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?

This is a simple two-parameter utility, but with no annotations, no output schema, and 0% parameter coverage, the description should have stated what the output looks like and what `tone=false` produces. As written, an agent can guess the happy path but cannot predict results or failure modes.

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 for both parameters and does not. It never explains the `tone` boolean (the obvious inference is that false drops tone marks, but whether it yields toneless or numbered pinyin is unstated), nor any constraint on `text` length or script.

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?

"Chinese text to pinyin with tone marks" names a specific transformation (transliteration) and its output format. It is unambiguous as to verb and resource, though it does not distinguish itself from any sibling, 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 Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, no mention of alternatives (e.g. a translation or dictionary tool), and no prerequisites. The agent must infer the use case entirely from the one-line purpose.

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.