Skip to main content
Glama

update_prospect_status

Move a prospect to a new pipeline stage (confirm-gated). Use list_prospects to get the id.

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": {
      "id": "<id>",
      "status": "<status>"
    },
    "name": "update_prospect_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
statusYes
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is largely covered. The description adds one genuinely behavioral fact, that execution is confirm-gated, but no detail on side effects such as notifications or whether stages can be moved backward.

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 terse sentences with zero filler, and the core action is front-loaded ahead of the prerequisite. Nothing could be removed without losing information.

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?

For a low-complexity mutation tool with no output schema, the definition covers purpose, prerequisite, and the confirm gate. It remains thin on what a preview response contains and on which stage transitions are legal, which matters for an enum-driven mutation.

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?

Schema coverage is only 33%, with only the confirm parameter documented structurally. The description partially compensates by indicating where the id comes from (list_prospects) and that status maps to a pipeline stage, but it never explains the enum values or whether arbitrary transitions are permitted.

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 states a specific verb and resource ('Move a prospect to a new pipeline stage'), which is far more informative than the tool name alone. It does not explicitly distinguish itself from adjacent siblings like assign_prospect or create_prospect, but the action is concrete enough that an agent can identify what it does.

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 supplies a real prerequisite chain: call list_prospects first to obtain the id. The '(confirm-gated)' note implies a preview-then-execute workflow, though the description never names an alternative tool or states a when-not-to-use condition.

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.