Tá Rodando

Atualizar monitor

atualizar_monitor

Idempotent

Altera nome, URL, intervalo, seção ou o texto que a resposta precisa conter (keyword) de um monitor. Só os campos enviados mudam; section: null tira o serviço da seção; keyword: null tira a checagem de texto. Num monitor privado, section publica: ele passa a aparecer na status page, nessa seção. A página inteira (várias seções, ordem, tirar da página) é editada por estruturar_pagina. URL ou keyword nova passa pela mesma validação de criar_monitor (url_failing só grava com confirmar: true).

Input Schema

Name	Required	Description
`id`	Yes	id do monitor (campo `id` de listar_monitores).
`url`	No	Nova URL pública a monitorar.
`name`	No	Novo nome do serviço.
`keyword`	No	Novo texto que a resposta precisa conter; null tira a checagem de texto.
`section`	No	Seção da status page (criada se não existir); num monitor privado, publica. null tira o serviço da seção.
`confirmar`	No	true = grava mesmo com a URL falhando agora (erro url_failing).
`intervalMin`	No	Intervalo de checagem em minutos: 5 ou 15 no free; 1, 5 ou 15 no pro.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 9, 2026

addedInput schema / properties / section / description

Added value: +"Seção da status page (criada se não existir); num monitor privado, publica. null tira o serviço da seção."

Changed1 schema field changedOct 8, 2026

addedInput schema / properties / keyword

Added value: +{
+  "anyOf": [
+    {
+      "description": "Texto que a resposta precisa conter (simples, diferencia maiúsculas). Resposta 2xx sem esse texto conta como falha: pega a página em branco que responde 200. Só o primeiro 1 MB do corpo é lido.",
+      "maxLength": 200,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Novo texto que a resposta precisa conter; null tira a checagem de texto."
+}

First observedOct 7, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Adds rich behavior beyond annotations: partial-update semantics, null handling for section and keyword, the side effect that section publishes a private monitor onto the status page, url_failing requiring confirmar:true, and 1 MB body read limit. This is exactly the context annotations (idempotentHint, destructiveHint) 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?

Dense but front-loaded with the changed fields, then side effects, then sibling routing. Slightly long with nested clauses, but every sentence carries distinct information.

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 7-param mutation tool with no output schema, the description covers partial updates, null semantics, side effects, validation gating, and sibling routing. An agent has what it needs to call correctly.

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. The description adds real meaning over the schema: null clears the field, section publishes a private monitor, and new URL/keyword goes through criar_monitor's validation. These are semantic rules the schema alone does not express.

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 (altera) and enumerates exactly which fields change (nome, URL, intervalo, seção, keyword), and explicitly names the sibling estruturar_pagina as the tool for page-level edits. An agent can distinguish it from atualizar_incidente and estruturar_pagina without opening schemas.

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 clear context: only sent fields change, and explicitly routes whole-page editing to estruturar_pagina. It also names criar_monitor as the source of validation rules. It lacks explicit when-not-to-use for partial-field cases, but the routing to the sibling is stated.

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

All Tá Rodando 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?