Skip to main content
Glama

Tommos

Move a company on the board «Prospecting»

move_a_company
Idempotent

Move a company on the board «Prospecting», as the signed-in person, as the board's press does: Pick a company in Found, or one with no stage that reads Prospect or Past (Picked gives it to Tommo SDR's job «Prospect a company»); move it to the next open stages; or put it in «Not now» with the reason, which the company keeps. to is one of: found (Found), picked (Picked), people_found (People found), outreach (Outreach), replied (Replied), not_now (Not now), disqualified (Disqualified). A company goes to Replied by itself when a person of the company writes to us: this tool does not move a company to Replied or out of it. A status is read, never moved. The move is a line of the company's history and of the audit trail, naming you. A refusal comes back in the board's words.

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": {
      "company_id": "<company_id>",
      "to": "<to>"
    },
    "name": "move_a_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesThe stage: found (Found), picked (Picked), people_found (People found), outreach (Outreach), replied (Replied), not_now (Not now), disqualified (Disqualified)
whyNoWith not_now: why, in the person's words
company_idYesThe company's id (from list_companies)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / to / description
      Previous value: -"The stage: found (Found), picked (Picked), people_found (People found), outreach (Outreach), replied (Replied), not_now (Not now)"New value: +"The stage: found (Found), picked (Picked), people_found (People found), outreach (Outreach), replied (Replied), not_now (Not now), disqualified (Disqualified)"
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly=false, idempotent=true, destructive=false, so the safety profile is covered; the description goes further by disclosing side effects: the move is recorded as a history line and audit-trail entry naming the caller, the not_now reason is retained, and refusals come back in the board's own wording. The prose is idiosyncratic ('as the board's press does') and the exact shape of a refusal is left vague, keeping it short of 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 purpose is front-loaded in the first clause, but the body is a single sprawling run-on sentence with metaphors that cost parsing effort, and it repeats the full stage enum that the input schema already documents. Trimming the duplicated enum and the figurative asides would materially improve it.

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 three-parameter mutation with no output schema, the description covers the important unknowns: automatic system-driven transitions, the exclusion of Replied, reason retention, audit/history side effects, and error signalling. Only the exact failure payload and stage-transition legality beyond Replied remain underspecified.

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 coverage is 100%, so the baseline would be 3, but the description adds meaning beyond the schema: it explains why the 'why' parameter matters ('with the reason, which the company keeps') and gives stage semantics, notably that Picked hands the company to Tommo SDR's job «Prospect a company». It also duplicates the enum list already present in the schema, which adds nothing.

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 opens with a specific verb+resource (move a company on the board «Prospecting») and enumerates the destination stages, so the agent knows exactly what operation this is. It is distinguishable from sibling mutations like move_deal or move_a_playbook_page by naming the company board, but it never explicitly contrasts itself with a sibling.

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?

It states eligibility (a company in Found, or one with no stage reading Prospect or Past) and gives an explicit exclusion: 'this tool does not move a company to Replied or out of it', plus 'A status is read, never moved.' That is real when/when-not guidance, but it never points at an alternative tool for the excluded cases (e.g. what to do when a company must leave Replied).

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.