pontofato

Contact

contact

Write to the people behind the product: a question, or a sponsorship/partnership/advertising proposal. One route for a question and for a sponsorship, partnership or ad proposal (tipo, with the placements of GET /api/partners). One message every 10 seconds per network: one that arrives sooner waits its turn and then goes out — no error. The message reaches the team by e-mail, with email as the reply address. For voice, send multipart/form-data: dados is this JSON (up to 32 KiB), and audio is one WebM, Ogg or M4A audio file (up to 2 MB). Audio can replace message. The browser records up to two minutes. Audio is attached to the owner's e-mail.

Input Schema

TableJSON Schema

Name	Required	Description
`fuso`	No	Consulting: the IANA time zone, such as `America/New_York`.
`name`	Yes	What to call the person writing.
`pais`	No	Consulting: the country of the person asking.
`site`	No	Website of who is proposing.
`tipo`	No	Proposal: `patrocinio`, `parceria`, `anuncio` or `consultoria`. Turns on the fields below.
`email`	Yes	Where to reply.
`prazo`	No	Consulting: when to start (`agora`, `1_mes`, `1_3_meses` or `explorando`).
`espaco`	No	Placement ids from `GET /api/partners`, up to 6.
`duracao`	No	Exposure in days: `30`, `90` or `365`.
`empresa`	No	Who is proposing, when it is a company.
`formato`	No	Consulting: `projeto` (per scope), `mensal` (monthly) or `assessoria` (advisory).
`message`	Yes	What you want to say.
`projeto`	No	Consulting: the kind of project (`llm_privado`, `voz`, `dados_sensiveis`, `gpu`, `integracao` or `outro`).
`horarios`	No	Consulting: up to 3 times for the call, `YYYY-MM-DDTHH:MM` in that time zone.
`whatsapp`	No	Optional reply number with country code, such as +5561999999999.
`orcamento`	No	Advertising: `ate_100`, `100_500`, `500_2000`, `2000_mais` or `a_combinar`. Consulting, in US dollars: `ate_2000`, `2000_5000`, `5000_10000`, `10000_mais` or `nao_sei`.
`pagamento`	No
`prefer_whatsapp`	No	Request a WhatsApp reply. Requires whatsapp.

Schema Changelog

Changes observed during successful MCP inspections.

Changed16 schema fields changedOct 15, 2026

changedInput schema / properties / duracao / description

Previous value: -"Dias de exposição: `30`, `90` ou `365`."New value: +"Exposure in days: `30`, `90` or `365`."

changedInput schema / properties / email / description

Previous value: -"Para onde responder."New value: +"Where to reply."

changedInput schema / properties / empresa / description

Previous value: -"Quem propõe, quando é empresa."New value: +"Who is proposing, when it is a company."

changedInput schema / properties / espaco / description

Previous value: -"Ids de placement de `GET /api/partners`, até 6."New value: +"Placement ids from `GET /api/partners`, up to 6."

changedInput schema / properties / formato / description

Previous value: -"Consultoria: `projeto` (por escopo), `mensal` ou `assessoria`."New value: +"Consulting: `projeto` (per scope), `mensal` (monthly) or `assessoria` (advisory)."

changedInput schema / properties / fuso / description

Previous value: -"Consultoria: o fuso IANA, como `America/New_York`."New value: +"Consulting: the IANA time zone, such as `America/New_York`."

changedInput schema / properties / horarios / description

Previous value: -"Consultoria: até 3 horários para a conversa, `AAAA-MM-DDTHH:MM` na hora do fuso."New value: +"Consulting: up to 3 times for the call, `YYYY-MM-DDTHH:MM` in that time zone."

changedInput schema / properties / message / description

Previous value: -"O que você quer dizer (alias `mensagem`)."New value: +"What you want to say."

changedInput schema / properties / name / description

Previous value: -"Como chamar quem escreve (alias `nome`)."New value: +"What to call the person writing."

changedInput schema / properties / orcamento / description

Previous value: -"Anúncio: `ate_100`, `100_500`, `500_2000`, `2000_mais` ou `a_combinar`. Consultoria, em dólar: `ate_2000`, `2000_5000`, `5000_10000`, `10000_mais` ou `nao_sei`."New value: +"Advertising: `ate_100`, `100_500`, `500_2000`, `2000_mais` or `a_combinar`. Consulting, in US dollars: `ate_2000`, `2000_5000`, `5000_10000`, `10000_mais` or `nao_sei`."

changedInput schema / properties / pais / description

Previous value: -"Consultoria: o país de quem pede."New value: +"Consulting: the country of the person asking."

changedInput schema / properties / prazo / description

Previous value: -"Consultoria: quando começar (`agora`, `1_mes`, `1_3_meses` ou `explorando`)."New value: +"Consulting: when to start (`agora`, `1_mes`, `1_3_meses` or `explorando`)."

changedInput schema / properties / prefer_whatsapp / description

Previous value: -"Request a reply through WhatsApp. Requires whatsapp."New value: +"Request a WhatsApp reply. Requires whatsapp."

changedInput schema / properties / projeto / description

Previous value: -"Consultoria: o tipo de projeto (`llm_privado`, `voz`, `dados_sensiveis`, `gpu`, `integracao` ou `outro`)."New value: +"Consulting: the kind of project (`llm_privado`, `voz`, `dados_sensiveis`, `gpu`, `integracao` or `outro`)."

changedInput schema / properties / site / description

Previous value: -"Site de quem propõe."New value: +"Website of who is proposing."

changedInput schema / properties / tipo / description

Previous value: -"Proposta: `patrocinio`, `parceria`, `anuncio` ou `consultoria`. Liga os campos abaixo."New value: +"Proposal: `patrocinio`, `parceria`, `anuncio` or `consultoria`. Turns on the fields below."

Changed2 schema fields changedOct 15, 2026

addedInput schema / properties / prefer_whatsapp

Added value: +{
+  "description": "Request a reply through WhatsApp. Requires whatsapp.",
+  "type": "boolean"
+}

addedInput schema / properties / whatsapp

Added value: +{
+  "description": "Optional reply number with country code, such as +5561999999999.",
+  "type": "string"
+}

Changed8 schema fields changedOct 15, 2026

addedInput schema / properties / formato / description

Added value: +"Consultoria: `projeto` (por escopo), `mensal` ou `assessoria`."

addedInput schema / properties / fuso / description

Added value: +"Consultoria: o fuso IANA, como `America/New_York`."

addedInput schema / properties / horarios / description

Added value: +"Consultoria: até 3 horários para a conversa, `AAAA-MM-DDTHH:MM` na hora do fuso."

changedInput schema / properties / orcamento / description

Previous value: -"`ate_100`, `100_500`, `500_2000`, `2000_mais` ou `a_combinar`."New value: +"Anúncio: `ate_100`, `100_500`, `500_2000`, `2000_mais` ou `a_combinar`. Consultoria, em dólar: `ate_2000`, `2000_5000`, `5000_10000`, `10000_mais` ou `nao_sei`."

addedInput schema / properties / pais / description

Added value: +"Consultoria: o país de quem pede."

addedInput schema / properties / prazo / description

Added value: +"Consultoria: quando começar (`agora`, `1_mes`, `1_3_meses` ou `explorando`)."

addedInput schema / properties / projeto / description

Added value: +"Consultoria: o tipo de projeto (`llm_privado`, `voz`, `dados_sensiveis`, `gpu`, `integracao` ou `outro`)."

changedInput schema / properties / tipo / description

Previous value: -"Proposta: `patrocinio`, `parceria` ou `anuncio`. Liga os campos abaixo."New value: +"Proposta: `patrocinio`, `parceria`, `anuncio` ou `consultoria`. Liga os campos abaixo."

Changed1 schema field changedOct 15, 2026
- removedInput schema / properties / pagamento / description
```
Removed value: -"`usdc`, `deposito` ou `a_combinar`."
```

Changed8 schema fields changedOct 15, 2026

addedInput schema / properties / formato

Added value: +{
+  "enum": [
+    "projeto",
+    "mensal",
+    "assessoria"
+  ],
+  "type": "string"
+}

addedInput schema / properties / fuso
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / horarios

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

changedInput schema / properties / orcamento / enum

Previous value: -[
-  "ate_100",
-  "100_500",
-  "500_2000",
-  "2000_mais",
-  "a_combinar"
-]New value: +[
+  "ate_100",
+  "100_500",
+  "500_2000",
+  "2000_mais",
+  "a_combinar",
+  "ate_2000",
+  "2000_5000",
+  "5000_10000",
+  "10000_mais",
+  "nao_sei"
+]

addedInput schema / properties / pais
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / prazo

Added value: +{
+  "enum": [
+    "agora",
+    "1_mes",
+    "1_3_meses",
+    "explorando"
+  ],
+  "type": "string"
+}

addedInput schema / properties / projeto

Added value: +{
+  "enum": [
+    "llm_privado",
+    "voz",
+    "dados_sensiveis",
+    "gpu",
+    "integracao",
+    "outro"
+  ],
+  "type": "string"
+}

changedInput schema / properties / tipo / enum

Previous value: -[
-  "patrocinio",
-  "parceria",
-  "anuncio"
-]New value: +[
+  "patrocinio",
+  "parceria",
+  "anuncio",
+  "consultoria"
+]

Changed3 schema fields changedSep 23, 2026

changedInput schema / properties / email / description

Previous value: -"E-mail de resposta."New value: +"Para onde responder."

changedInput schema / properties / message / description

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

changedInput schema / properties / name / description

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

Changed7 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"
+}

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"
+}

Changed3 schema fields changedSep 6, 2026
- addedInput schema / properties / email / description
```
Added value: +"E-mail de resposta."
```
- addedInput schema / properties / message / description
```
Added value: +"Mensagem (alias `mensagem`)."
```
- addedInput schema / properties / name / description
```
Added value: +"Nome (alias `nome`)."
```
First observedSep 6, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Annotations only declare non-read-only, non-idempotent, non-destructive; the description goes well beyond that. It discloses the queueing rate-limit behavior (a message arriving sooner waits its turn, no error), that delivery is by e-mail with `email` as reply address, the multipart/form-data alternate path with exact size caps (32 KiB JSON, 2 MB audio), and accepted audio formats.

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?

Purpose is front-loaded and most sentences carry real information (rate limit, multipart, delivery). There is mild redundancy between the first sentence and the 'One route for a question and for a sponsorship...' sentence, and the mention of `GET /api/partners` as a separate route is slightly disorienting.

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?

For an 18-parameter tool with no output schema and 94% schema coverage, the description covers behavior well: limits, queueing, delivery, and the alternate voice format. It omits any statement about the success/failure response or authentication, which is a modest remaining gap given no output schema exists.

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 94%, so the schema carries most parameter meaning (baseline 3). The description adds genuinely non-schema information: the behavior of `tipo` turning on dependent fields, and the entire multipart `dados`/`audio` input format that does not appear in the JSON schema at all.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Write to the people behind the product', and enumerates the two supported cases (a question, or a sponsorship/partnership/ad proposal). The phrasing is slightly loose ('the people behind the product'), but an agent immediately knows this is the contact/submission tool, and no sibling overlaps with it.

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?

It explains the selector (`tipo`) that switches between a question route and the proposal fields, and states the rate-limiting behavior (one message every 10 seconds per network, queued rather than errored). It does not give explicit when-not-to-use guidance, but with no competing sibling that gap is minor.

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

All pontofato 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.

Contact

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources