SurveyBridge AI

Overview Schema Source Related Servers Discussions Admin

surveybridge_export_project

Export a documented local SurveyBridge project bundle to a new output directory, optionally choosing CSV, JSON, Excel, or notebook formats for auditable sharing.

Instructions

Export a documented local bundle under SURVEYBRIDGE_OUTPUT_ROOT to a new directory only.

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": {
      "project_id": "<project_id>",
      "output_dir": "<output_dir>"
    },
    "name": "surveybridge_export_project"
  }
}

Input Schema

Name	Required	Description	Default
`formats`	No
`output_dir`	Yes
`project_id`	Yes

Output Schema

Name	Required	Default
`data`	No
`source`	No
`status`	No	ok
`warnings`	No
`truncated`	No
`pagination`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 2, 2026

TDQS

C2.9/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two useful behaviors: output is confined under SURVEYBRIDGE_OUTPUT_ROOT and the destination must be a new directory (so no overwrite). It says nothing about permissions, whether partial exports can occur, or the meaning of 'documented' bundle, so disclosure is partial only.

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?

A single tight sentence with the location constraint front-loaded and no filler. It is efficient, though at this brevity it borders on under-specification rather than optimal conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described, but with an unannotated write tool, 0% parameter documentation, and an unexplained 'documented bundle', the description is too thin. An agent cannot confidently predict what formats are accepted or what side effects to expect.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 3 parameters, and the description adds meaning only for output_dir ('new directory only'). Neither project_id nor formats (including what format strings are legal) is clarified anywhere, so the agent must guess at the most consequential argument.

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 (Export) and resource (a documented local bundle for a project), plus a scoping constraint under SURVEYBRIDGE_OUTPUT_ROOT. It is clearly distinguishable from the read-oriented siblings (list/search/get), though what 'documented bundle' contains is left vague.

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?

The phrase 'to a new directory only' implies the target must not already exist, which is a usage constraint, but there is no explicit when-to-use, prerequisites, or mention of alternatives. Given the sibling set contains no other export tool, the lack of routing guidance is a real gap.

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

Deploy Server