Skip to main content
Glama
Sign In

Ania

by solutions.diatech
OverviewDiscussionsAdmin

Skip a movement

skip_movement

Leaves one movement out of the avatar when the user gives up on it. Ania asks the user (confirmation form); without one, the tool returns the question: ask it and call again with user_confirmed: true only after an explicit yes. Never decide for the user.

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": {
      "jobId": "<jobId>",
      "state": "<state>",
      "reason": "<reason>"
    },
    "name": "skip_movement"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYesThe job id from criar_avatar or ver_andamento.
stateYesState id as listed by ver_andamento.
reasonYesThe user’s reason, in their words.
languageNoThe user's language as a BCP-47 tag (e.g. 'en', 'en-US', 'pt-BR', 'es'). Replies and prices follow it.
user_confirmedNoOnly without a confirmation prompt: true only after the user explicitly said yes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare the safety profile (not read-only, not destructive), whereas the description adds genuinely non-obvious behavior: an internal confirmation form may be raised, and without it the tool returns the question rather than acting. It stops short of saying whether a skip is reversible or what the job state becomes afterward.

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?

Three sentences, front-loaded with what the tool does before the procedural confirmation detail. The parenthetical '(confirmation form)' is slightly vague but no sentence is wasted.

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 non-destructive state mutation with full schema coverage and no output schema, the description covers the key hazard: agent-initiated confirmation. The main omission is any statement about what the user loses or whether the skip can be undone.

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

Parameters3/5

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

Schema coverage is 100%, so the schema already documents jobId, state, reason, language, and user_confirmed. The description reinforces the gating semantics of user_confirmed but adds nothing for reason or language, so the baseline 3 applies.

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?

Uses a concrete verb+resource: 'Leaves one movement out of the avatar', which is clearly distinct from approve_movement or redo_movement semantics. It doesn't explicitly name a sibling to route away from, so it lands at a clear-but-undifferentiated 4.

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

Usage Guidelines4/5

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

Gives a clear trigger condition ('when the user gives up on it') and an explicit exclusion: never decide for the user, and only pass user_confirmed after an explicit yes. It lacks any statement of when to prefer skip over approve/redo, which keeps it below 5.

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