Skip to main content
Glama

Trumpet: emails and views

trumpet_contact

Trumpet™: for up to 10 creators the founder picked (keys from trumpet_find), their email (influencers.club, only a validated one, never guessed), whether they did brand deals, their bio, and their average views from their recent posts. $0.28 for each creator with an email; one without costs nothing.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "keys": "<keys>"
    },
    "name": "trumpet_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
keysYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations only mark this as non-read-only, open-world, and non-destructive; the description goes well beyond that by disclosing per-record cost ($0.28), that records without a found email are free, the external data source (influencers.club), and the policy that only validated emails are returned, never guessed. That pricing and data-quality context is exactly what an agent needs before spending money. It stops short of describing latency or partial-failure behavior on a 10-key batch.

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

Conciseness5/5

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

Two sentences, front-loaded with the product and the returned fields, then the cost model. Every clause carries information — scope, input provenance, output fields, source, validation policy, and price — with no filler.

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

Completeness5/5

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

For a one-parameter, paid, open-world lookup with no output schema, the definition covers the input source, the batch limit, the returned fields, cost semantics, and data provenance. An agent can decide whether to call it and predict the charge without reading anything else.

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 0%, so the description carries the burden, and it does: "keys" are identified as the founder-picked creators from trumpet_find, and the 10-record cap is stated in prose as well as enforced by maxItems. It still does not say what a key looks like or what happens if one is invalid or unresolvable.

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 names the exact payload it returns for a bounded set of records: email, brand-deal history, bio, and average recent views, for up to 10 creators. It also ties itself to the sibling that supplies its input ("keys from trumpet_find"), so an agent can place it in the workflow. It loses a point only because the retrieval verb is implicit rather than stated.

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?

The parenthetical "keys from trumpet_find" is a real usage hint: it tells the agent this is the downstream enrichment step after discovery and where to get identifiers. However, it never states when to prefer this tool over alternatives, when not to call it, or that it should be reserved for a shortlist already vetted by the founder.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources