Radar noEixo

Create product

create_product

Cria um novo produto ou serviço no catálogo. Produtos ativos passam a ser incluídos automaticamente no contexto do agente, em toda resposta. É AQUI que mora o preço de produto ou serviço (campo price, ex.: "A partir de R$ 32.900") — não no system_prompt nem na base de conhecimento, para não ter dois valores divergindo. Informação que o agente deve PERGUNTAR ao cliente não é produto: vai em order_fields (update_agent_config).

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": {
      "name": "<name>",
      "type": "<type>",
      "description": "<description>"
    },
    "name": "create_product"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Nome do produto ou serviço
`type`	Yes	Tipo: "physical" (produto físico), "recurring" (assinatura/recorrente), "service" (serviço avulso)
`price`	No	Preço em formato livre, ex: "R$ 99,90" ou "A partir de R$ 200"
`features`	No	Características adicionais, benefícios ou observações (opcional)
`description`	Yes	Descrição detalhada do produto para o agente usar no contexto

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 26, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare non-readonly, non-destructive, closed-world. The description adds a real behavioral consequence the annotations cannot express: active products are automatically injected into the agent's context on every response. It stops short of stating what happens on duplicate names, how inactive products behave, or what is returned.

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?

Four sentences, each carrying distinct information: purpose, side effect, price placement, and exclusion rule. Front-loaded and no filler, though the capitalization emphasis and cross-reference parentheticals add slight noise.

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?

Covers the create action, the side effect of active products, the field-placement rule that prevents divergent prices, and where non-product data should go instead. With a fully described schema and clear annotations, nothing an agent needs to call this correctly 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 baseline is 3, but the description adds genuine meaning: it pins the price value to the `price` field with a free-form format example and forbids duplicating it in the system prompt or knowledge base. The remaining parameters (name, type, features) are left to the schema.

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?

Opens with a specific verb+resource ("Cria um novo produto ou serviço no catálogo") and then defines the entity boundary: what counts as a product vs. what belongs in order_fields or the system prompt. An agent can tell this apart from update_product/list_products without opening either schema.

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?

Explicitly names a competing destination for adjacent data ("Informação que o agente deve PERGUNTAR ao cliente não é produto: vai em order_fields (update_agent_config)") and says where price must live. It does not cover update-vs-create disambiguation, but the routing guidance is unusually concrete.

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?