Skip to main content
Glama
Sign In

Tokfluence

by com.tokfluence
OverviewDiscussionsAdmin

Plan a creator list from a brief

plan_creator_list
Read-onlyIdempotent

START HERE for any request to find creators or build a list. Call this before search_creators, every time, even when the brief sounds clear.

It costs nothing and changes nothing. It returns the questions you should put to the user before spending their credits, plus a concrete search plan.

Why it matters: a one-line brief almost never says how many creators are wanted, what they are for, or which attributes are dealbreakers, and those answers change the entire result. Asking four short questions first is the difference between a list the user can act on and seven names that happen to match a keyword.

Ask the questions it returns, wait for the answers, then follow the plan.

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": {
      "brief": "<brief>"
    },
    "name": "plan_creator_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
briefYesThe user's request, in their own words. Paste it as they wrote it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already declare readOnlyHint and destructiveHint=false, but the description adds the credit-economics angle ('costs nothing', 'before spending their credits'), which is the trait that actually matters to the caller. It describes the shape of the return value at a high level (questions + search plan) and that it mutates nothing. It does not describe the plan's structure or length, which keeps it from a 5.

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?

The imperative lead is well front-loaded, but the 'Why it matters' paragraph is persuasive padding that repeats the same idea twice ('seven names that happen to match a keyword'). The core instruction could be delivered in half the words without losing meaning.

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 one-parameter, non-destructive planning tool with no output schema, the description covers the essentials: what it returns, that it is free, and the required follow-up action. Only the structure of the returned plan/questions is left implicit, which is a minor gap.

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?

There is a single parameter with 100% schema description coverage, so the baseline is 3. The description explains why the brief matters ('a one-line brief almost never says how many creators are wanted'), but adds no format or content guidance beyond the schema's own 'paste it as they wrote it'.

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?

States a specific verb and resource ('plan a creator list from a brief') and explicitly names what it returns: the questions to put to the user plus a concrete search plan. It also distinguishes itself from the sibling search_creators by positioning itself upstream of it.

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

Usage Guidelines5/5

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

Gives an unambiguous entry condition ('START HERE for any request to find creators'), names the alternative it precedes (search_creators) and even removes the common exclusion ('even when the brief sounds clear'). It also prescribes the follow-up sequence: ask the returned questions, wait, then follow the plan.

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

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