Skip to main content
Glama
Sign In
ClickHouse Loom

ClickHouse Loom

Official
by ClickHouse
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

loom_op

Run Loom operations not exposed as a listed tool by passing the dotted op name and its arguments; use op="help" with a query to discover matching ops and their parameters.

Instructions

Run an op this list doesn't show (such as memory.related, callable by name). op is the dotted name, arguments its arguments; op="help" with an optional query lists matching ops and their args. Prefer a listed tool when one fits.

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": {
      "op": "<op>"
    },
    "name": "loom_op"
  }
}

Input Schema

NameRequiredDescriptionDefault
opYes
queryNo
argumentsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, so the safety profile is partly covered, and the description usefully discloses the help/query introspection mechanism. However, it says nothing about the fact that an arbitrary dispatcher can execute ops of unknown effect, nor what happens on an invalid op name. It does not contradict the annotations.

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 tight sentences, front-loaded with the core purpose, then parameter roles, then the sibling-preference rule. Every clause carries information; nothing is redundant.

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 three-parameter dispatcher with a nested object and no output schema, the definition covers selection and parameter roles but omits return behavior, error handling for unknown ops, and any warning that dispatched ops may mutate state. Adequate to call, not fully complete.

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 description coverage is 0%, so the description must compensate, and it does: `op` is identified as a dotted name, `arguments` as its arguments, and `query` as the optional filter used with op="help". The nested `arguments` object's shape stays opaque, but the description points to help output as the way to discover per-op args.

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?

The description states a specific verb and resource ('Run an op') and scopes it to ops 'this list doesn't show', with a concrete example (memory.related) and a discovery mode (op="help"). It is clearly differentiated from the listed loom_* siblings, though the nature of the 'op' universe remains abstract.

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

Usage Guidelines5/5

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

It gives explicit when-to-use ('an op this list doesn't show'), explicit when-not ('Prefer a listed tool when one fits'), and a fallback discovery path (op="help" with optional `query`). An agent has no inference left to make about selecting this tool versus a sibling.

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