Skip to main content
Glama
xuanji86

FastBound MCP

by xuanji86
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Lock disposition

lock_disposition
Idempotent

Prevent further edits to a disposition record with a dry-run preview by default. Pass confirm:true to execute the write lock.

Instructions

Lock a disposition to prevent further edits. Dry-run by default; pass confirm:true. Write.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesGUID of the disposition to lock.
accountNoWhich configured FastBound account to use for this one call — an alias or account number (see list_accounts). Omit to use the active account.
confirmNoSet true to actually execute. Omit or false returns a DRY RUN preview that sends nothing.
auditUserNoEmail recorded as X-AuditUser for the ATF audit trail. Overrides FASTBOUND_AUDIT_USER for this call. Must be an active user on the account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.0
    • addedInput schema / properties / account
      Added value: +{
+  "description": "Which configured FastBound account to use for this one call — an alias or account number (see list_accounts). Omit to use the active account.",
+  "type": "string"
+}
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations, the description clearly discloses that the operation is a write and that it is dry-run by default unless confirm:true is passed. This is essential behavioral information for an agent to avoid unintended side effects. It does not cover edge cases like re-locking or locked-state errors, but it adds meaningful value beyond the annotations.

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?

The description is extremely concise: three short clauses, each earning its place. The primary action is front-loaded, the dry-run caveat is immediately given, and the 'Write' note clarifies the mutation behavior without wasting words.

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?

Given the annotations, complete parameter documentation, and no output schema, the description is largely sufficient for invocation. It explains the key operational nuance (dry-run by default) and the write nature of the call. It could add detail about return values or what happens after a disposition is locked, but nothing essential to calling the tool correctly is missing.

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 description coverage is 100%, so all four parameters are already documented in the schema. The description only restates the confirm parameter's role ('pass confirm:true'), adding little semantic value beyond what the schema already provides. Baseline 3 is appropriate.

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?

The description names a specific verb ('Lock'), a specific resource ('disposition'), and the intended effect ('prevent further edits'). It is clearly distinct from sibling tools like delete_disposition or commit_disposition, so an agent can immediately tell what this tool is for.

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?

The description gives clear context for when to use the tool: to lock a disposition against further edits. It also explains the critical dry-run vs. confirm execution mode. However, it does not explicitly name alternatives or state when not to use this tool, such as when the goal is merely to commit rather than lock.

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

Deploy Server

Other Tools