Agentalog — Agent Auto Log

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 (type, 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

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.

Changed2 schema fields changedOct 15, 2026

addedInput schema / properties / prefer_whatsapp

Added value: +{
+  "description": "Request a WhatsApp reply. 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: +"Consulting: `projeto` (per scope), `mensal` (monthly) or `assessoria` (advisory)."

addedInput schema / properties / fuso / description

Added value: +"Consulting: the IANA time zone, such as `America/New_York`."

addedInput schema / properties / horarios / description

Added value: +"Consulting: up to 3 times for the call, `YYYY-MM-DDTHH:MM` in that time zone."

changedInput schema / properties / orcamento / description

Previous value: -"`ate_100`, `100_500`, `500_2000`, `2000_mais` or `a_combinar`."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`."

addedInput schema / properties / pais / description

Added value: +"Consulting: the country of the person asking."

addedInput schema / properties / prazo / description

Added value: +"Consulting: when to start (`agora`, `1_mes`, `1_3_meses` or `explorando`)."

addedInput schema / properties / projeto / description

Added value: +"Consulting: the kind of project (`llm_privado`, `voz`, `dados_sensiveis`, `gpu`, `integracao` or `outro`)."

changedInput schema / properties / tipo / description

Previous value: -"Proposal: `patrocinio`, `parceria` or `anuncio`. Turns on the fields below."New value: +"Proposal: `patrocinio`, `parceria`, `anuncio` or `consultoria`. Turns on the fields below."

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

Changed8 schema fields changedOct 14, 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"
+]

Changed8 schema fields changedSep 9, 2026

addedInput schema / properties / duracao

Added value: +{
+  "description": "Exposure in days: `30`, `90` or `365`.",
+  "enum": [
+    "30",
+    "90",
+    "365"
+  ],
+  "type": "string"
+}

addedInput schema / properties / empresa

Added value: +{
+  "description": "Who is proposing, when it is a company.",
+  "type": "string"
+}

addedInput schema / properties / espaco

Added value: +{
+  "description": "Placement ids from `GET /api/partners`, up to 6.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

removedInput schema / properties / form_ts

Removed value: -{
-  "description": "When the form was opened; the anti-robot of the human path, and only it requires this.",
-  "type": "number"
-}

addedInput schema / properties / orcamento

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

addedInput schema / properties / pagamento

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

addedInput schema / properties / site

Added value: +{
+  "description": "Website of who is proposing.",
+  "type": "string"
+}

addedInput schema / properties / tipo

Added value: +{
+  "description": "Proposal: `patrocinio`, `parceria` or `anuncio`. Turns on the fields below.",
+  "enum": [
+    "patrocinio",
+    "parceria",
+    "anuncio"
+  ],
+  "type": "string"
+}

Changed1 schema field changedSep 9, 2026

changedInput schema / properties / form_ts / description

Previous value: -"When the form was opened; it is the anti-robot of the human path."New value: +"When the form was opened; the anti-robot of the human path, and only it requires this."

Changed4 schema fields changedSep 6, 2026
- addedInput schema / properties / email / description
```
Added value: +"Where to reply."
```
- addedInput schema / properties / form_ts / description
```
Added value: +"When the form was opened; it is the anti-robot of the human path."
```
- addedInput schema / properties / message / description
```
Added value: +"What you want to say."
```
- addedInput schema / properties / name / description
```
Added value: +"What to call the person writing."
```
First observedSep 5, 2026

TDQS

A3.9/5.0

Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, idempotentHint=false, destructiveHint=false): it discloses a 10-second-per-network rate limit with queueing rather than erroring, email delivery with `email` as reply address, the multipart/form-data voice path, and explicit size caps (32 KiB JSON, 2 MB audio, 2-minute recording). This is exactly the operational context annotations cannot carry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

Purpose and rate limit are front-loaded, and most sentences carry information, but the phrasing is awkward and roundabout ('one that arrives sooner waits its turn and then goes out — no error'), and the multipart details are buried at the end rather than scoped to the voice use case.

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, the description covers rate limits, delivery channel, reply routing, enum-driven modes, and the voice upload path. It omits only minor details such as what a successful submission returns, which is low-stakes since no output schema is defined.

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 baseline is 3, but the description adds real value the schema cannot: the multipart/form-data structure for voice (`dados` carrying this JSON plus an `audio` file) and that audio may replace `message`. These transport-level parameters do not appear as schema properties, so the description is doing necessary work.

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+resource: 'Write to the people behind the product', and enumerates the accepted intents (question, sponsorship/partnership/ad proposal). It does not name any sibling, but no sibling tool overlaps with 'contact', so differentiation is implicit and unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It implies when to use the tool ('One route for a question and for a sponsorship, partnership or ad proposal') and even maps `type` to the placements endpoint, but gives no when-not guidance and names no alternative route. Usage is inferable rather than stated.

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

All Agentalog — Agent Auto Log tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Contact

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources