Skip to main content
Glama

Paying customers Shipfound brought

customers_brought
Read-only

Revenue share: each paying customer of the product, from its payment provider (read hourly), whether Shipfound brought them and through which shipped work (a page, a listing or post, a tagged link, an ad it made), or why not (another way, the founder's own ads, a customer before, more than 90 days after the visit), what they paid and the share; this month's share charged, owed and the cap; and why paid jobs wait, when a share cannot be charged. 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": "customers_brought"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare this a safe, read-only, closed-world tool. The description adds substantial behavioral context beyond them: hourly reading from the payment provider, the 90-day attribution window, the attribution reasons (another way, founder's own ads, prior customer), and share caps that can block paid jobs, but it says nothing about return shape, volume, or pagination.

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 writing is a single ~90-word run-on sentence joined by commas and semicolons, and it does not front-load a verb or a summary of the operation. Little is padded, but the wall of clauses is hard to parse at a glance.

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?

With no parameters, no output schema, and annotations that already imply read-only behavior, the description is largely complete on data provenance and revenue-share mechanics. However, without an output schema it should say more about the shape or granularity of what comes back, and it lacks any usage context.

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?

The tool has zero parameters, so the input schema already covers everything. A baseline of 4 is warranted because the description does not misrepresent the no-argument call and implies the result is scoped server-side by product.

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 recounts the tool's content in detail: every paying customer, whether Shipfound sourced them, which shipped work did so, what they paid, and the revenue share. However, there is no leading verb, no explicit 'returns/lists', and the opening noun phrase 'Revenue share:' makes an agent work out the resource and operation from a run-on sentence.

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?

The description gives no guidance on when to use this tool versus alternatives; only the trailing 'Free.' hints at cost. There is no mention of when to prefer it over analytics or revenue siblings, and no prerequisites or exclusions.

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