Skip to main content
Glama

meta-agent-tools

by br.app.classificado
OverviewDiscussionsAdmin

Contact

contact

Write to the people behind the product: a question, or a sponsorship/partnership/advertising proposal. Free, no captcha and no payment; one message every 10 s per network (one that arrives sooner waits its turn). One route for a question and for a sponsorship, partnership or ad proposal (tipo, with the placements of GET /api/partners). No captcha, no account, no payment. 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
NameRequiredDescriptionDefault
nameYesWhat to call the person writing.
siteNoWebsite of who is proposing.
tipoNoProposal: `patrocinio`, `parceria` or `anuncio`. Turns on the fields below.
emailYesWhere to reply.
espacoNoPlacement ids from `GET /api/partners`, up to 6.
duracaoNoExposure in days: `30`, `90` or `365`.
empresaNoWho is proposing, when it is a company.
messageYesWhat you want to say.
orcamentoNo`ate_100`, `100_500`, `500_2000`, `2000_mais` or `a_combinar`.
pagamentoNo`usdc`, `deposito` or `a_combinar`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • 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"
+}
  2. Changed1 schema field changed
    • 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."
  3. Changed4 schema fields changed
    • 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."
  4. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations it discloses substantial behavioral traits: no captcha, no account, no payment required; a rate limit of one message per 10 s per network; and the exact overflow behavior (a sooner-arriving message waits its turn rather than erroring). It also explains delivery — the message reaches the team by e-mail and `email` becomes the reply address.

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 is front-loaded, which is good, but the text repeats itself for no gain: 'Free, no captcha and no payment' is restated as 'No captcha, no account, no payment,' and the 10-second-per-network queue rule is stated twice in near-identical wording. The parenthetical insertions also make it denser than needed.

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 a 10-parameter, non-read-only, non-idempotent tool with full schema coverage, the description covers what matters: no auth/payment, throttling behavior, and message delivery. Since there is no output schema, it could say more about the success/error response, but the queueing note covers the main failure mode.

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 description coverage is already 100%, so the baseline is 3, but the description adds real meaning: `tipo` selects the proposal route and its `espaco` placement ids come from `GET /api/partners`, and `email` is used as the reply address in the delivered e-mail. It does not, however, explain field applicability per `tipo` value beyond noting that the proposal fields turn on.

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 resource: write a question or a sponsorship/partnership/ad proposal to the people behind the product. That is unambiguous and cannot be confused with any sibling (billing, endpoints, environments, etc.), though it never explicitly differentiates itself from a named alternative.

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 usage context: use it for a question or for a sponsorship/partnership/ad proposal, and states that a single route serves both cases via `tipo`. No exclusions or named alternatives are offered, but with no competing sibling there is little to disambiguate.

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 toolsInspect
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