Skip to main content
Glama

AutoTasker Hub — China Social Data API

random_bear_image

Random bear image URL via placebear placeholder service. $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": "random_bear_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
widthNo
heightNo

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 real context the schema cannot supply: the data comes from placebear and each call costs $0.01 USDC. It omits return form (presumably a URL string), whether the call is idempotent/cacheable, and any rate or failure behavior, so the disclosure is partial rather than complete.

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 short sentences with the core purpose front-loaded and no filler. The trailing '$0.01 USDC.' is a fragment, but it delivers high-value cost information compactly, so it earns its place.

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 trivial two-parameter image tool with no output schema, the description covers source and cost, which is most of what matters. It still leaves the meaning and effect of width/height undocumented when cost (per call) is involved, so it is adequate but not complete.

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% and the description never mentions width or height, leaving the agent to interpret them solely from property names and bare defaults of 600. The dimensions are somewhat self-evident, but the definition does nothing to compensate for the coverage 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?

The description names a specific verb-like outcome (random bear image URL) and resource, and identifies the backing service (placebear). The resource name alone separates it from siblings such as random_cat_image and random_dog_image, though no sibling is explicitly referenced.

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 statement of when to use this tool versus the cat/dog equivalents or random_dog_placeholder, and no prerequisites or exclusions are given. Usage is only implied by the phrase 'placeholder service', which an agent must infer.

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.