Skip to main content
Glama

hookpulse

by net.hookpulse
OverviewDiscussionsAdmin

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. Changed9 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"
+}
    • changedInput schema / required
      Previous value: -[
-  "name",
-  "email",
-  "message",
-  "form_ts"
-]New value: +[
+  "name",
+  "email",
+  "message"
+]
  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

A3.9/5.0
Behavior4/5

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

No annotations are provided, so the description carries the behavioral disclosure burden. It states that no captcha, account, or payment is required, describes a 10-second queued rate limit per network, explains that earlier messages wait and then send without error, and says the message reaches the team by e-mail with `email` as 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.

Conciseness2/5

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

The description is repetitive: 'Free, no captcha and no payment' and the 10-second queuing rule appear twice in nearly identical wording. It is front-loaded with the core purpose, but the redundancy makes it longer and less efficient than it should be.

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?

The tool has no annotations and no output schema, but the description covers the purpose, recipient, reply address, constraints, rate-limiting/queue behavior, and conditional proposal path. Minor omissions such as expected validation errors or response shape are not critical for a contact-form-like tool.

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 coverage is 100%, so the baseline is 3. The description adds some useful context around `tipo` and the proposal flow, but most parameter-level meaning is already provided by the schema descriptions. It does not substantially expand parameter semantics beyond the schema.

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?

The description opens with a precise action and target: 'Write to the people behind the product: a question, or a sponsorship/partnership/advertising proposal.' This makes the tool's purpose clear and distinguishes it from the unrelated sibling tools without relying on the generic name 'contact'.

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?

The description explicitly states when to use the tool: for questions, sponsorship, partnership, or advertising proposals. It also explains the conditional proposal route via `tipo` and `GET /api/partners`. It does not mention exclusions or alternative tools, but no sibling tool is a direct alternative.

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

All hookpulse 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