Skip to main content
Glama

block_addable_types

Lists block types that can be safely created with the block_add operation, so you can choose valid types before adding logic blocks.

Instructions

Lists the block types that block_add can create safely.

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": "block_addable_types"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations exist, so the description carries the full disclosure burden, yet it only implies this is a read operation via the verb 'Lists'. It says nothing about whether the list is project-scoped or static, whether results are cached, or what form the entries take (names vs. identifiers), which matters because block_add presumably consumes those identifiers.

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?

A single front-loaded sentence with no filler. It is efficient, though slightly terse given the safety qualifier ('create safely') is left unexplained.

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?

For a zero-parameter list tool with no output schema, the description should at least indicate what the returned entries are (type names or IDs) since block_add needs them. It establishes the tool's role but stops short of telling the agent how to use the results.

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 and the schema is empty, so there is no parameter meaning to convey; baseline 4 applies. The description correctly adds no parameter detail because none exists.

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?

States a specific verb and resource ('Lists the block types') plus a qualifier ('that block_add can create safely') that ties it to the write sibling. An agent can tell it apart from catalog_list_types and catalog_get_type, though the distinction from the catalog tools is only implied by the 'block_add-safe' framing.

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 implied rather than stated: the phrase 'that block_add can create safely' hints this is a discovery step before calling block_add, but the description never says 'call this before block_add' or excludes the catalog_* alternatives. The agent must infer the when-to-use condition.

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