Skip to main content
Glama

get_block

Get one Bencho block in full: the React component (TSX), its CSS, the npm packages it needs, its settings, and a usage line. Pass values to set its settings (by setting id) in the usage line.

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": {
      "id": "<id>"
    },
    "name": "get_block"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe block id, from search_blocks.
valuesNoOptional setting values by id, e.g. { "corner": 12 }.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and does well: it names exactly what is returned (code, CSS, packages, settings, usage line) and explains that `values` changes how the usage line renders. It stops short of stating that this is a pure read with no side effects, or warning that full TSX+CSS payloads can be large.

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?

Two sentences with no filler; the return payload is front-loaded and the secondary `values` behavior follows. Nothing could be removed without losing information.

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?

No output schema exists, so the description must characterize the return value, and it does so by enumerating the five payload parts. It leaves the exact shape of the response (how settings and packages are keyed) unspecified, which is a minor gap for a tool with a nested `values` object.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: `values` sets the block's settings by id and is reflected in the usage line, which the schema's 'Optional setting values by id' does not convey. `id` is framed as coming from search_blocks, reinforcing the lookup workflow.

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?

Specific verb (get) and resource (one Bencho block) with the payload enumerated: TSX component, CSS, npm packages, settings, usage line. The phrase 'one ... in full' implicitly contrasts with the sibling search_blocks, but that distinction is inferred rather than stated explicitly.

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?

Usage is only implied: fetch a single block in full, presumably after locating it via search_blocks (the id parameter's schema description points there). There is no explicit when-to-use/when-not statement or named alternative such as search_blocks for listing many blocks.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources