Radar noEixo

Create agent link

create_agent_link

Cria um link de entrada para um agente: quando a PRIMEIRA mensagem de uma conversa nova bate com o texto (sem acento nem maiúscula, tolera pouca edição), a conversa vai direto a esse agente, sem menu. Use um link por origem (site, Instagram, anúncio, cartão) para medir de onde vêm as conversas. O texto é único no número. Devolve o endereço wa.me para publicar.

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": {
      "agent_profile_id": "<agent_profile_id>",
      "nome": "<nome>",
      "texto": "<texto>"
    },
    "name": "create_agent_link"
  }
}

Input Schema

Name	Required	Description
`nome`	Yes	Nome da origem: "Site", "Instagram", "Cartão de visita" (até 40)
`texto`	Yes	Texto pronto que o cliente manda, ex.: "Olá! Vim pelo site do Seu Lima" (8 a 200)
`numero_id`	No	id do número do link (list_agent_profiles → numeros). Vazio = qualquer número em que o agente trabalha
`target_user_id`	No	(Só o admin da plataforma) userId da conta a operar
`agent_profile_id`	Yes	id do agente (list_agent_profiles)

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 31, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), and the description adds real behavioral detail beyond them: accent/case-insensitive matching with tolerance for small edits, the uniqueness constraint ('O texto é único no número'), and the returned wa.me address. It doesn't cover failure modes (e.g. what happens on a duplicate text), so it stops short of a 5.

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?

Roughly four sentences, front-loaded with the core behavior and followed by the usage pattern, the uniqueness constraint, and the return value. Dense but every sentence carries information; only the parenthetical matching detail borders on over-explanation.

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?

With five parameters, no output schema, and no nested objects, the description fills the important gaps: it explains the link's runtime behavior and states what is returned ('Devolve o endereço wa.me'), compensating for the missing output schema. Admin-only targeting is left to the parameter description.

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, but the description adds meaning beyond the schema by tying the uniqueness rule to the texto/numero_id pair — telling the agent that the same text cannot be reused on the same number. That is constraint knowledge the property descriptions do not state.

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?

Names a specific verb+resource ('Cria um link de entrada para um agente') and immediately defines the mechanism: a first-message text match routes a new conversation directly to that agent, bypassing the menu. This is clearly distinguishable from siblings like create_agent_profile or set_agent_menu.

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?

'Use um link por origem (site, Instagram, anúncio, cartão) para medir de onde vêm as conversas' gives a concrete usage pattern and rationale. It does not name an alternative tool or state when not to use it, but the triggering mechanism makes the appropriate context clear.

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

All Radar noEixo tools Inspect

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

Need Help?