Skip to main content
Glama
Sign In

Symbola

by io.github.spikinglabs
OverviewDiscussionsAdmin

Read decisions

read_decisions
Read-onlyIdempotent

The decisions a pack makes: each one a rule a builder could get wrong, with its status (decided, default or open). Narrow them to one component or to decisions mentioning some words.

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": {
      "pack": "<pack>"
    },
    "name": "read_decisions"
  }
}

Input Schema

NameRequiredDescriptionDefault
packYesThe pack id, owner/name, e.g. kausalflow/lightkone. A symbola.sh pack link works too.
queryNoOnly decisions whose id or text contains all of these words.
statusNoOnly decisions with this status.
componentNoOnly decisions checked in this component, e.g. search-query.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add domain context — and it does, characterizing each result as a rule with a status of decided/default/open. It stops short of describing ordering, result size, or what happens when a pack has no decisions, which is the main remaining gap for a read tool.

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?

Two tight sentences with the resource definition front-loaded and the filtering hint second — no wasted clauses. Minor looseness in 'some words' and 'one component' where the description is gesturing at the schema rather than saying something precise.

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?

For a four-parameter read tool with full schema coverage, a complete annotation set, and no output schema, the description covers what the tool returns and how to filter it. Only the absence of return-shape or empty-result behavior keeps it from being fully self-sufficient.

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 description coverage is 100%, so the parameter contract is fully documented in structured data and the baseline is 3. The description reinforces the intent of component and query ('decisions mentioning some words') but adds no syntax, matching behavior, or edge-case semantics beyond what the schema already states.

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 names a specific resource (the decisions a pack makes) and explains what a decision record actually is — a rule a builder could get wrong — plus its status vocabulary. It's clearer than a bare 'read' verb, but it doesn't distinguish itself from siblings like read_pack_file or get_pack, which an agent may see as plausible alternatives for pack-scoped data.

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?

Filtering guidance is present ('Narrow them to one component or to decisions mentioning some words'), which implies when to pass component/query. However, there's no explicit statement of when to use this versus read_pack_file or get_pack, and no mention of prerequisites like needing the pack to exist.

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

All Symbola toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources