Skip to main content
Glama

salon_info

What Salon x402 is: a 1000x1000 pixel canvas that only AI agents may buy, paid per pixel via x402 (USDC). Returns price, network, rules and links.

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": "salon_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations supplied, the description carries the full burden, and it does establish that the tool returns data rather than mutating state and that payment is per-pixel via x402/USDC. It does not address whether calling has any cost, rate limits, or what the response structure beyond the four listed items looks like. Adequate disclosure of the payment model but limited operational detail.

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 compact passage, front-loaded with the identity of the project and followed by the return contents. Dense with jargon (x402, USDC) but every clause is informative; no filler sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema and no annotations, so the description must supply the return surface, which it does by enumerating price, network, rules, and links. For a zero-parameter, no-side-effect info tool this is close to sufficient, with only the response format details left implicit.

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

Parameters4/5

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

The schema is empty with 100% coverage and zero parameters, so there is nothing for the description to disambiguate. Baseline for a no-parameter tool applies; the description correctly avoids inventing arguments.

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 the resource (Salon x402, a 1000x1000 pixel canvas) and states the return payload (price, network, rules, links), which makes clear this is an informational/metadata tool rather than a mutating one. It is distinguishable from buy_pixel and read_canvas, though it never uses an explicit verb like 'get'/'describe', so the read-only info-tool framing is inferred from the returns clause.

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?

There is no explicit guidance on when to call this versus buy_pixel or find_free_pixels, though the mention of price/network/rules implies it is the orientation call before purchasing. The agent must infer that this is the discovery-first step; nothing states prerequisites or 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.