Skip to main content
Glama
Sign In

Ania

by solutions.diatech
OverviewDiscussionsAdmin

Search avatars

search_avatars
Read-only

Show the Ania avatar catalogue. Call this whenever the user wants to see, browse, list, search or pick an Ania avatar — "show me some Ania avatars", "what avatars do you have", "mostre os avatares da Ania". Never generate an image instead: these are real marketplace listings, and a generated picture cannot be installed. The results render as an interactive gallery, so do not describe them afterwards.

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

Input Schema

NameRequiredDescriptionDefault
sortNo
limitNo
queryNoFree text, e.g. 'cyberpunk woman'
categoryNoCategory slug
free_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already establish read-only, non-destructive, open-world behavior, and the description adds what they cannot: the results are real marketplace listings that can be installed, and they render as an interactive gallery that the agent should not narrate afterwards. That rendering instruction is directly actionable and prevents a common failure mode.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core action is stated in the first clause, followed by trigger guidance, then the anti-pattern, then the output-handling note. Every sentence carries a distinct instruction and nothing is repeated from the schema.

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?

For a read-only listing tool with no output schema, the description covers the important non-obvious behavior: real listings versus generated images and gallery rendering. The remaining gap is parameter behavior — sorting, page size and the free_only filter are undocumented anywhere, which matters for a browse tool.

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 only 40% — only query and category are documented, while sort, limit and free_only carry no explanation. The description says nothing about any parameter, so it does not compensate; notably the free_only default of true and the 1-24 limit range are left for the agent to infer.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a concrete verb and resource ('Show the Ania avatar catalogue') and enumerates the supported intents: see, browse, list, search, pick. It also explicitly separates this tool from image generation, so an agent can tell what class of action this is without opening the schema.

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

Usage Guidelines5/5

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

It gives an explicit trigger condition ('whenever the user wants to see, browse, list, search or pick an Ania avatar') backed by sample utterances in two languages, and an explicit anti-pattern ('Never generate an image instead') with the reason. That is a when-to-use plus a when-not-to-use in one place.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Ania toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources