Skip to main content
Glama

Trumpet: the creators

trumpet

Trumpet™: the creators found for this product's buyers (influencers.club), each with their status (found, contact: email and views in, written, replied, deal, posted, paid), their tagged link, their average views, the three ways to pay them priced at the founder's price per 1,000 views (options: flat, perView with its cap, upfrontBonus), and for posted ones what their post brought by its link. cpmUsd: the founder's price per 1,000 average views, asked once and kept. mark: one step for one creator (written, replied, deal with model flat, per_view or upfront_bonus and its numbers, posted with the post's link: recorded with its campaign so its visits, signups and revenue are read, paid with what the founder paid, skip). Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "trumpet"
  }
}

Input Schema

NameRequiredDescriptionDefault
markNo
cpmUsdNoThe founder's price per 1,000 average views, in dollars

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior4/5

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

Annotations establish that this is a non-read-only mutation, and the description adds concrete behavioral context: mark advances one creator through named statuses, posted links are recorded with campaign attribution for visits/signups/revenue, paid records founder payment, and cpmUsd is 'asked once and kept.' It still omits idempotency, permissions, and what happens when both cpmUsd and mark are supplied, but it meaningfully exceeds the annotations.

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 a single dense run-on with trademark branding, duplicated status enumerations, and no front-loaded action statement. Useful details are present, but the structure makes them hard to scan and 'Free.' adds little.

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?

It partially covers return contents (status, linked tag, average views, payment options, post results) and mutation behavior, which matters because there is no output schema. Still, with a nested mark object, it leaves key identifiers, deal subfield mappings, and the tool's behavior when no parameters are supplied unclear.

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?

The description explains cpmUsd's persistence and maps many mark.action values to real-world meanings (written, replied, deal, posted, paid, skip) and deal models. However, it never defines the key parameter and only vaguely refers to deal 'numbers,' leaving amountUsd, per1000Usd, bonusUsd, and bonusAtViews undocumented beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource—creators found for a product's buyers—and enumerates statuses and outputs, but it never uses a clear action verb or states whether the primary operation is listing creators, recording a mark, setting CPM, or all three. It is more specific than tautology, but the agent must infer the tool's primary action.

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

Usage Guidelines2/5

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

No explicit when-to-use guidance, exclusions, or comparison to siblings such as trumpet_find or trumpet_contact. The 'Free.' note and mark description imply usage but do not tell an agent when this tool is the right choice.

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