Skip to main content
Glama
Sign In
bruno-mcp

bruno-mcp

by TheDMPV
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get a Bruno endpoint

get_endpoint

Retrieve a sanitized endpoint contract by stable ID or exact method and normalized path. Access complete API contract details without executing requests.

Instructions

Returns a complete sanitized endpoint contract by stable ID, or by exact method and normalized path.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_endpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
pathNo
methodNo
include_examplesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It mentions 'sanitized' without explanation, and omits auth requirements, rate limits, or side effects. The tool is a read operation, but this is not explicitly stated.

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?

The description is a single sentence with no extraneous information. It is concise but could benefit from additional structuring to separate retrieval modes.

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?

Given 4 parameters, no output schema, and sibling tools for listing, the description does not cover return format, error cases, or how it complements other tools. It is incomplete for reliable agent invocation.

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?

With 0% schema description coverage, the description must compensate by explaining parameters. It only maps two parameters (id, path/method) vaguely. Missing include_examples and the meaning of 'normalized path' are not explained.

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 it returns a sanitized endpoint contract by stable ID or by method and path. This distinguishes it from sibling tools like list_endpoints and search_endpoints, which handle multiple endpoints.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when you have a specific endpoint identifier or route, but it does not explicitly state when to use this tool over alternatives like list_endpoints or search_endpoints. No exclusions or conditions are given.

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