Skip to main content
Glama
xuanji86

FastBound MCP

by xuanji86
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get disposition

get_disposition
Read-only

Retrieve a disposition record by FastBound GUID or external ID. Read-only lookup for quick verification.

Instructions

Retrieve a single disposition by FastBound GUID id or your externalId. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe id value to look up.
idTypeNoWhether `id` is the FastBound GUID (default) or your externalId.
accountNoWhich configured FastBound account to use for this one call — an alias or account number (see list_accounts). Omit to use the active 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/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description merely repeats 'Read-only' without adding context beyond that. The description does not disclose what happens on not-found or whether the response includes related items, but given the annotations carry the safety profile, a baseline 3 is appropriate.

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?

A single sentence with zero waste. The purpose and key id-type distinction are front-loaded, and every word carries meaning.

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 straightforward get-by-id operation with annotations covering read-only and open-world behavior, the description is adequately complete. It does not describe the return payload, but no output schema exists and the tool's simplicity reduces the need. A minor gap is the lack of any note about the `account` parameter, though the schema covers it.

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 descriptions cover 100% of the three parameters, including the idType enum semantics. The description only echoes the id type distinction and adds no syntax or format details beyond what the schema already provides. With high schema coverage, the baseline 3 holds.

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 clearly states a specific verb ('Retrieve') and a precise resource ('a single disposition'), and explicitly names the two identifier types (FastBound GUID id or externalId). This distinguishes it from sibling tools like search_dispositions, which retrieve multiple records, and from get_acquisition, which targets a different resource.

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 provides clear context for when to use the tool: when you have a specific disposition identifier. It even clarifies the two id types via the parameter mention. However, it does not explicitly mention alternatives or exclusions (e.g., 'use search_dispositions for filtering'), so it stops short of full guidance.

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