Skip to main content
Glama

Block model reference

get_block_model
Read-only

Returns the qu4zr workspace, block, and link schema with JS runtime notes, client version, supported platform features, and an example to guide correct builds.

Instructions

Returns the qu4zr workspace/block/link schema, the JS runtime notes, this client's version and the platform features it knows about, plus an example. Read this before building.

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_block_model"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.53.0

TDQS

A3.8/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description's job is to add context — and it does, by disclosing that the response bundles schema, runtime notes, client version, feature list, and an example. It does not say whether the content is version-specific, static, or how large the payload is, which are the remaining behavioral gaps.

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?

One sentence, front-loaded with the verb and the returned artifacts, closing with the actionable directive. The enumerated list is dense but each item describes actual payload content, so little is wasted.

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?

With no output schema and no parameters, the description must carry the return-value burden itself, and it enumerates the contents plus notes an example is included. Minor gap: it does not indicate freshness or scope of the 'client's version' and 'platform features' fields, which an agent might want when deciding whether to re-call.

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?

The tool takes zero parameters, so there is no parameter meaning to convey and the baseline of 4 applies. The description correctly avoids inventing arguments.

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?

"Returns the qu4zr workspace/block/link schema, the JS runtime notes, this client's version and the platform features... plus an example" names a concrete verb and enumerates the exact payload, so an agent knows this is the reference/spec tool rather than a block operation. It stops short of explicitly contrasting itself with delete_block/test_block/update_block, which is why it is not a 5.

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?

"Read this before building" gives a clear trigger condition for calling it. There are no exclusions or named alternatives, but for a zero-parameter lookup tool the when-to-use signal is unambiguous.

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