Skip to main content
Glama

AutoTasker Hub — China Social Data API

pypi_info

PyPI package metadata: latest version, summary, license, requires_python, author, classifiers. $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": {
      "package": "<package>"
    },
    "name": "pypi_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
packageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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. It usefully discloses the $0.01 USDC cost, which is real behavioral context an agent needs before calling, and it lists the returned fields. However, it says nothing about behavior for a nonexistent or misspelled package, version resolution rules, or whether results are cached.

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 compact fragments, purpose first, cost trailing. Nothing is padded, though the bare '$0.01 USDC.' fragment reads as a tacked-on note rather than integrated information.

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 one-parameter, no-output-schema tool, listing the returned fields does substitute for a return schema and the cost note covers the payment side. Still missing is parameter format guidance and failure behavior, which matter for a paid call that can fail on bad input.

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

Parameters3/5

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

Schema description coverage is 0%, so the 'package' parameter is undocumented anywhere. The identifier format (bare name vs. version pin, case sensitivity, normalization) is left unstated, though a single required 'package' string is largely self-explanatory.

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?

States a concrete resource and operation: PyPI package metadata, and enumerates the returned fields (latest version, summary, license, requires_python, author, classifiers). An agent can tell this is a single-package lookup rather than a search, but the description never names or contrasts any sibling such as crates_search.

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 prerequisites, and no mention of alternatives (e.g., searching vs. fetching a known package). The use case is only implied by the phrase 'PyPI package metadata'.

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.