Skip to main content
Glama
Sign In
Bruno MCP Server

Bruno MCP Server

by jcr82
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

bruno_validate_collection

Validate a Bruno collection's structure and configuration to ensure correctness and consistency before running API tests.

Instructions

Validate a Bruno collection's structure and configuration

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": {
      "collectionPath": "<collectionPath>"
    },
    "name": "bruno_validate_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
collectionPathYesPath to the Bruno collection to validate

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description should disclose behavioral traits like read-only or side effects. Only a single sentence stating what it does, with no elaboration on outcomes (errors, return values, or modifications).

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?

Single sentence with no superfluous words. However, it could be more informative without increasing length significantly.

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?

Given the simplicity of the tool (one param, no output schema), the description provides the basic purpose but lacks contextual details like what validation entails or expected output, which an agent might need for correct invocation.

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?

The single parameter collectionPath is fully described in the schema (100% coverage). The description adds no further meaning beyond 'path to the Bruno collection', so baseline of 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 uses a specific verb 'Validate' and resource 'Bruno collection's structure and configuration', clearly distinguishing it from siblings like run_collection or validate_environment.

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?

No guidance on when to use this tool vs alternatives (e.g., before running a collection, or if wanting to validate an environment). Usage context is only implied.

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