Skip to main content
Glama
Sign In

Radar noEixo

by com.noeixodigital
OverviewDiscussionsAdmin

Set conversation agent

set_conversation_agent
DestructiveIdempotent

Troca à mão o agente que atende uma conversa (para corrigir ou testar). agent_profile_id "entrada" devolve a conversa ao agente de entrada. Não manda mensagem ao cliente: o agente novo responde a partir da próxima mensagem dele. Fica uma nota interna na conversa.

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": {
      "conversation_id": "<conversation_id>",
      "agent_profile_id": "<agent_profile_id>"
    },
    "name": "set_conversation_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
target_user_idNo(Só o admin da plataforma) userId da conta a operar
conversation_idYesid da conversa
agent_profile_idYesid do agente (list_agent_profiles) ou "entrada"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

With readOnlyHint=false and destructiveHint=true already declared, the description adds real behavioral detail: no message is sent to the customer, the new agent answers only from the customer's next message, and an internal note is logged on the conversation. It also explains the special reset effect of the "entrada" value, which annotations cannot convey.

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 short sentences, front-loaded with the action, then the special value, then the side effects. Nothing is redundant, though the parenthetical could be folded in without loss.

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?

No output schema exists, so the description carries the return-behavior burden, and it does so by stating no customer message is sent and a note is left behind. The admin-only scope of target_user_id is only in the schema, but that is covered elsewhere.

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?

Schema coverage is 100%, so the baseline is 3; the description earns above that by explaining that agent_profile_id="entrada" returns the conversation to the entry agent, adding semantics the schema only hints at. target_user_id is left to the schema, which documents it adequately.

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 verb and resource: it manually swaps which agent handles a conversation, and it names the use cases (corrigir ou testar). That is clearly distinguishable from update_agent_profile or get_agent_config, though it never names a sibling to route against.

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?

"Para corrigir ou testar" gives a clear context for when to reach for this tool instead of editing the agent profile. It lacks explicit when-not guidance or a named alternative, but the suggested scenario is unambiguous.

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

All Radar noEixo 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