Skip to main content
Glama

Set path in

crm_set_path_in
Destructive

Replace the ordered "how we get in" plan for an account. The bullets replace the previous set whole — a plan is one coherent thing, not a pile of appended thoughts. The old plan stays in the audit trail. Effects: path-in bullets replaced.

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": {
      "account_id": "<account_id>",
      "bullets": "<bullets>"
    },
    "name": "crm_set_path_in"
  }
}

Input Schema

NameRequiredDescriptionDefault
bulletsYesThe plan, in order.
account_idYesThe account. An existing account id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, and the description genuinely adds to that: it clarifies that the entire prior set is destroyed rather than appended to, and that the old plan remains in the audit trail, which speaks to recoverability. It does not cover permissions or validation failures, so it falls short of full transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action, then the replacement rule, then a compact effects line. The closing 'Effects: path-in bullets replaced.' largely restates the second sentence, so it is a small amount of duplicated content rather than wasted prose.

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 two-parameter mutation with full schema coverage and explicit destructive/idempotency annotations, the description supplies what annotations cannot: that the write is a full overwrite and that prior state persists in audit history. Only the absence of guidance about partial edits or permissions keeps it from being fully complete.

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 is 3; the description earns a step above by explaining that the bullet array is an ordered, whole-replacement payload ('a plan is one coherent thing, not a pile of appended thoughts'), which is semantics the schema does not convey. It adds no detail on account_id beyond the schema's own wording.

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?

States a specific verb and resource: 'Replace the ordered "how we get in" plan for an account.' The replacement semantics (whole-set overwrite, not append) make the operation distinct from the other 'set' siblings. It stops short of naming a contrasting sibling, but the resource is unambiguous.

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?

There is no when-to-use / when-not-to-use guidance and no mention of alternatives (e.g. a tool for appending or editing a single bullet). The reader must infer from the sibling list whether this is the right tool for a partial edit. The only usage-adjacent statement is that the bullets replace the previous set whole, which is semantics rather than routing guidance.

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.