Skip to main content
Glama

AutoTasker Hub — China Social Data API

random_dog_placeholder

Random dog placeholder image (placeholder.dog). $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_dog_placeholder"
  }
}

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 of behavioral disclosure. It usefully states the $0.01 USDC cost and source service, which are important for a paid tool, but it does not explain billing mechanics, return format, or whether dimensions affect pricing.

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?

The description is a single efficient sentence with no wasted wording. The core purpose is front-loaded, followed by the source and price, though the price notation is slightly abrupt.

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 simple two-optional-parameter image tool with no output schema, the description is adequate but incomplete. An agent knows what it returns conceptually and that it costs $0.01 USDC, but lacks return-format and parameter-behavior details.

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 does not mention the width or height parameters at all. Their names and defaults are self-explanatory in the schema, but the description adds no meaning such as size limits, aspect-ratio behavior, or pricing impact.

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 states a specific resource, a random dog placeholder image, and names the source domain placeholder.dog. It is clear what the tool produces, but it does not explicitly distinguish itself from the sibling random_dog_image tool.

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 guidance on when to use this placeholder-image tool versus the sibling random_dog_image tool. The price note hints at a paid placeholder use case, but no explicit selection criteria or exclusions are provided.

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.