buildin-mcp

by ekho

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Get Buildin block

buildin_get_block

Retrieve a block object from a Buildin workspace by its ID, excluding child blocks.

Instructions

Retrieve a single block object by ID. Does not include children.

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": {
      "block_id": "<block_id>"
    },
    "name": "buildin_get_block"
  }
}

Input Schema

Name	Required	Description	Default
`block_id`	Yes	Buildin object ID (UUID-like).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1Jun 18, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Clearly states it does not include children, a key behavioral trait. No annotations exist, but description covers basic read behavior.

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?

Single succinct sentence, front-loaded with purpose, zero wasted 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?

Adequate for a simple retrieval tool with one parameter and no output schema. Describes operation and a key behavioral constraint, though no mention of error handling or return format.

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 coverage is 100% with description for block_id. Tool description adds no new meaning beyond the schema's 'Buildin object ID (UUID-like).' Baseline 3 applies.

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?

Verb 'Retrieve' + resource 'single block object by ID' explicitly states purpose. Differentiates from sibling buildin_get_block_children by noting it does not include children.

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?

Implies when to use (retrieve block without children) and differentiates from children-fetching sibling, but no explicit mention of when-not or alternative tools.

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