Skip to main content
Glama

Start facts on request (spends credits)

start_facts_on_request

SPENDS CREDITS: quote_facts_on_request first, show the price to the user and after their yes pass its credits as confirm_credits. The work runs in the background; poll get_search / list_leads. [REST: POST /api/tasks/{id}/manual]

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": {
      "task_id": "<task_id>",
      "cids": "<cids>",
      "confirm_credits": "<confirm_credits>"
    },
    "name": "start_facts_on_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
cidsYesPerson ids (cid) from list_leads.
promoteNo
task_idYesThe search id (task id), e.g. from list_searches or create_search.
confirm_creditsYesThe price in credits the matching quote returned, shown to the user and confirmed by them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Adds substantial context beyond the annotations: the operation spends credits, requires an explicit user confirmation gated on a prior quote, and executes asynchronously so the agent must poll. The annotations already flag non-read-only and non-idempotent behavior. Not covered is what happens on a repeat invocation or a rejected confirm_credits (error vs. charge).

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 dense sentences plus an endpoint tag, with the spend warning front-loaded so it cannot be missed. Every clause carries actionable information (prerequisite, confirmation gate, argument source, background/polling behavior); nothing is filler.

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 4-parameter mutation with no output schema, the description supplies the critical call-correctly information: the prerequisite quote, the confirmation requirement, and the async polling pattern. It omits what the call returns (e.g. a task/run id) and the semantics of `promote`, which an agent would otherwise have to guess.

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?

With 75% schema coverage the baseline is 3, and the description earns above that by explaining where confirm_credits comes from and why it must match the quote — meaning the schema alone does not convey. The `promote` parameter is undocumented in both schema and description, and the cids/task_id provenance is already in 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 leads with a cost warning and a workflow rather than stating what the tool actually does; the verb and resource ('start fact-finding on selected person ids') must be inferred from the name/title plus the phrase 'The work runs in the background'. It is distinguishable from quote_facts_on_request through the credits hand-off, but an agent reading only the description body would not get a clean statement of the action.

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?

Strong explicit sequencing: call quote_facts_on_request first, show the price to the user, and only after their yes pass its `credits` as confirm_credits. It also names the follow-up tools (get_search, list_leads) to poll after starting. It stops short of stating exclusions, e.g. what to do if a run is already in progress or if the user declines.

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