Radar noEixo

Create tag

create_tag

Cria uma etiqueta na conta SEM pôr em nenhum contato, para deixá-la pronta antes do primeiro uso (ex.: "Comercializadora: Electra" antes da primeira indicação). Ela passa a aparecer no seletor de etiquetas do contato e no editor de automações. Não dispara automação. Recusa nome repetido (ignora maiúscula e acento) e nome reservado do sistema. Para pôr a etiqueta num contato, use add_contact_tag.

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": {
      "nome": "<nome>"
    },
    "name": "create_tag"
  }
}

Input Schema

Name	Required	Description	Default
`nome`	Yes	Nome da etiqueta, até 60 caracteres
`para_que_serve`	No	Opcional: uma linha dizendo quando usar, mostrada à equipe (até 140 caracteres)

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 31, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only declare the generic write/safe/non-open-world profile. The description adds real behavioral context the annotations cannot: it does not fire automations, it rejects duplicate names case- and accent-insensitively, it rejects reserved system names, and the result becomes visible in the contact tag picker and automation editor.

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?

Front-loaded with the crucial constraint in the first clause, and each following sentence adds distinct information (visibility, no automation trigger, validation rules, alternative tool). It is dense but every sentence earns its place; only the parenthetical example could be trimmed.

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

Completeness5/5

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

For a two-parameter mutation with no output schema, the description covers side effects, visibility, validation failures, and the sibling handoff. Nothing an agent needs in order to call it correctly, or to predict its failure modes, is missing.

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 both parameters are already documented. The description still adds meaning for 'nome' by specifying the uniqueness rule (case/accent-insensitive) and reserved-name rejection, which are validation semantics the schema does not carry. 'para_que_serve' is left to the schema, which is acceptable given full coverage.

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?

States a specific verb and resource (create a tag on the account) and immediately scopes it negatively: it does NOT attach the tag to any contact. That negative scope is exactly what separates it from the sibling add_contact_tag, so the agent can route correctly on name alone.

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?

Gives the intended use case with a concrete example ('Comercializadora: Electra' before the first indication) and names the alternative tool for the other job ('Para pôr a etiqueta num contato, use add_contact_tag'). When-to-use and when-to-use-something-else are both explicit.

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?