Skip to main content
Glama

AutoTasker Hub — China Social Data API

ip_geo

IP geolocation: country, region, city, ASN. $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": {
      "ip": "<ip>"
    },
    "name": "ip_geo"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipYes

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?

No annotations are supplied, so the description carries the full burden. It does disclose a genuine behavioral trait the schema cannot express — the $0.01 USDC cost, warning of a paid call — but says nothing about invalid/malformed IP handling, rate limits, latency, or the response shape beyond field names.

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?

A single terse line that front-loads the operation, then the outputs, then the price — every token carries information. It is telegraphic rather than ungrammatical, so nothing is wasted, but the fragment style leaves gaps a complete sentence could close.

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 lookup with no annotations and no output schema, listing the returned fields partially substitutes for a return schema and the price disclosure is valuable. It still falls short on input format rules and failure behavior, which matter for a paid call.

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 coverage is 0% for the single `ip` parameter, and the description never specifies accepted formats (IPv4 vs IPv6 vs hostname) or whether private/reserved ranges work. The word 'IP' in the description is the only signal, so it barely compensates for the documentation gap.

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?

Names a specific resource (IP) and operation (geolocation) and enumerates the returned fields: country, region, city, ASN. It is instantly distinguishable from every listed sibling, none of which are IP-related, though it does not explicitly contrast with alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is only implied by the topic: an agent infers it should call this when it needs geographic/ASN data for an address. There is no statement of when to prefer it over another source, no prerequisites, and no exclusions.

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.