grade

Contact

contact

Fale com quem faz o produto: dúvida, ou proposta de patrocínio/parceria/anúncio. Grátis, sem captcha nem pagamento; uma mensagem a cada 10 s por rede (a que chega antes espera a vez). Uma rota para dúvida e para proposta de patrocínio, parceria ou anúncio (tipo, com os espaços de GET /api/partners). Sem captcha, sem conta, sem pagamento. Uma mensagem a cada 10 segundos por rede: a que chega antes espera a vez e sai — sem erro. A mensagem chega à equipe por e-mail, com o email como endereço de resposta.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Como chamar quem escreve (alias `nome`).
`site`	No	Site de quem propõe.
`tipo`	No	Proposta: `patrocinio`, `parceria` ou `anuncio`. Liga os campos abaixo.
`email`	Yes	Para onde responder.
`espaco`	No	Ids de placement de `GET /api/partners`, até 6.
`duracao`	No	Dias de exposição: `30`, `90` ou `365`.
`empresa`	No	Quem propõe, quando é empresa.
`message`	Yes	O que você quer dizer (alias `mensagem`).
`orcamento`	No	`ate_100`, `100_500`, `500_2000`, `2000_mais` ou `a_combinar`.
`pagamento`	No	`usdc`, `deposito` ou `a_combinar`.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 23, 2026

changedInput schema / properties / message / description

Previous value: -"O que você quer dizer."New value: +"O que você quer dizer (alias `mensagem`)."

changedInput schema / properties / name / description

Previous value: -"Como chamar quem escreveu."New value: +"Como chamar quem escreve (alias `nome`)."

Changed9 schema fields changedSep 9, 2026

addedInput schema / properties / duracao

Added value: +{
+  "description": "Dias de exposição: `30`, `90` ou `365`.",
+  "enum": [
+    "30",
+    "90",
+    "365"
+  ],
+  "type": "string"
+}

addedInput schema / properties / empresa

Added value: +{
+  "description": "Quem propõe, quando é empresa.",
+  "type": "string"
+}

addedInput schema / properties / espaco

Added value: +{
+  "description": "Ids de placement de `GET /api/partners`, até 6.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

removedInput schema / properties / form_ts

Removed value: -{
-  "description": "Início da composição, em milissegundos Unix: entre 2 segundos e 12 horas atrás, obrigatório também para agentes.",
-  "type": "integer"
-}

addedInput schema / properties / orcamento

Added value: +{
+  "description": "`ate_100`, `100_500`, `500_2000`, `2000_mais` ou `a_combinar`.",
+  "enum": [
+    "ate_100",
+    "100_500",
+    "500_2000",
+    "2000_mais",
+    "a_combinar"
+  ],
+  "type": "string"
+}

addedInput schema / properties / pagamento

Added value: +{
+  "description": "`usdc`, `deposito` ou `a_combinar`.",
+  "enum": [
+    "usdc",
+    "deposito",
+    "a_combinar"
+  ],
+  "type": "string"
+}

addedInput schema / properties / site

Added value: +{
+  "description": "Site de quem propõe.",
+  "type": "string"
+}

addedInput schema / properties / tipo

Added value: +{
+  "description": "Proposta: `patrocinio`, `parceria` ou `anuncio`. Liga os campos abaixo.",
+  "enum": [
+    "patrocinio",
+    "parceria",
+    "anuncio"
+  ],
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "name",
-  "email",
-  "message",
-  "form_ts"
-]New value: +[
+  "name",
+  "email",
+  "message"
+]

Changed4 schema fields changedSep 6, 2026

addedInput schema / properties / email / description
```
Added value: +"Para onde responder."
```

addedInput schema / properties / form_ts / description

Added value: +"Início da composição, em milissegundos Unix: entre 2 segundos e 12 horas atrás, obrigatório também para agentes."

addedInput schema / properties / message / description
```
Added value: +"O que você quer dizer."
```
addedInput schema / properties / name / description
```
Added value: +"Como chamar quem escreveu."
```

First observedSep 6, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations only declare readOnly=false, idempotent=false, destructive=false, so the description carries most of the burden and does deliver: no captcha, no account, no payment, one message per 10s per network with queuing instead of an error, and delivery to the team via email with `email` as reply-to. The disclosure is real, but the rate-limit/delivery facts are restated rather than expanded, 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.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded, but the body is heavily redundant: the 10-second rate limit is stated twice, and 'sem captcha / sem conta / sem pagamento' appears three times in slightly varied wording. Roughly half the sentences could be deleted with no loss of information.

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 no output schema, the description usefully explains the observable outcome (message reaches the team by email, email used as reply-to) plus auth and rate-limit behavior for a 10-parameter write tool. Nothing an agent needs to call it correctly appears to be missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and every field is documented, including enums and aliases. The description adds only marginal meaning (that `tipo` binds the proposal fields and that `email` becomes the reply address), so the baseline 3 for schema-complete tools is correct.

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+resource ('Fale com quem faz o produto') and explicitly names the two intents it covers: dúvida and sponsorship/partnership/ad proposals. An agent can distinguish this contact tool from every media-oriented sibling (chat_send, post_comment, etc.) without opening the 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?

Clearly says when to use it (a question, or a sponsorship/partnership/ad proposal) and ties the proposal path to the `tipo` field and the slots of `GET /api/partners`. It does not name an alternative tool or state exclusions, but no sibling covers the same ground, so the routing guidance is adequate.

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

All grade 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?