meta-agent-tools

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.

Input Schema

TableJSON Schema

Name	Required	Description
`fuso`	No
`name`	Yes	What to call the person writing.
`pais`	No
`site`	No	Website of who is proposing.
`tipo`	No	Proposal: `patrocinio`, `parceria` or `anuncio`. Turns on the fields below.
`email`	Yes	Where to reply.
`prazo`	No
`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
`message`	Yes	What you want to say.
`projeto`	No
`horarios`	No
`orcamento`	No	`ate_100`, `100_500`, `500_2000`, `2000_mais` or `a_combinar`.
`pagamento`	No

Schema Changelog

Changes observed during successful MCP inspections.

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.8/5.0

Behavior4/5

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

Annotations (readOnlyHint=false, idempotentHint=false, destructiveHint=false) already declare the write and non-destructive profile, so the description is not carrying the safety burden. It goes further by disclosing a rate limit with queue semantics — 'One message every 10 seconds per network: one that arrives sooner waits its turn and then goes out — no error' — which is genuinely actionable, plus the delivery path ('reaches the team by e-mail, with `email` as the reply address'). It does not say whether submissions are acknowledged or deduplicated.

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?

Three sentences, front-loaded with the purpose, and each sentence contributes something (intent routing, rate limiting, delivery). The middle sentence ('One route for a question and for a sponsorship, partnership or ad proposal (`tipo`, with the placements of `GET /api/partners`)') is syntactically tangled and forces a re-read, which costs it a point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 16-parameter tool with 7 enums and no output schema, the description covers the transport mechanics well but not the form itself. It never explains the branching structure implied by `tipo` (which fields apply to a question vs. each proposal kind), nor the seven undocumented parameters. Adequate, but an agent filling this out is left guessing about roughly half the fields.

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 only 56% across 16 parameters, several of which (`fuso`, `pais`, `prazo`, `formato`, `projeto`, `horarios`, `pagamento`) are documented nowhere. The description does add real value for two fields, linking `espaco` to placement ids from `GET /api/partners` and `email` to the reply address, but it leaves the majority of under-documented parameters unexplained, so it neither fully compensates nor is redundant with the schema.

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 states a specific verb and target: 'Write to the people behind the product', and enumerates the two supported intents (a question, or a sponsorship/partnership/advertising proposal). That is enough for an agent to know the tool submits a contact message. It stops short of naming the resource formally (a contact/lead submission endpoint) and reads a little colloquially, but the purpose is unambiguous.

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 gives clear context for when to reach for this tool — 'One route for a question and for a sponsorship, partnership or ad proposal' — and ties the proposal branch to `tipo` and `GET /api/partners` placements. There are no explicit exclusions or named alternatives, but the sibling list contains no competing contact/submission tool, so the routing guidance present is sufficient.

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

All meta-agent-tools tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?