Skip to main content
Glama

What Matters

by com.blackdogranch

get_document

Read everything: action items, the record of what has already been dismissed, and "focus" — the handful of terms the user says matter most. Always call this before proposing changes: it is the only way to know what was already deleted or rejected, and re-suggesting those is the main failure mode.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
include_rulesNoInclude the standing rules. Default true. Read them: the server drops any suggestion an active rule excludes, so proposing one is wasted effort.
include_dismissedNoInclude deleted items and previously rejected suggestions. Default true, and you almost always want it: this is how you avoid proposing something again.

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description explains the importance of calling this read tool to avoid failure modes. However, it doesn't explicitly mention side effects or auth, but the read-only nature is clear from 'Read everything' and the guidance to call before changes.

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 that are direct and front-loaded, with no redundant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description mentions the return contents (action items, dismissed, focus) and the workflow context, making it complete for a read tool without an output schema.

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 covers both parameters with detailed descriptions about include_rules and include_dismissed defaults and implications. The tool description does not add parameter-specific details, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool reads action items, dismissed records, and focus terms. It uses the verb 'Read' and specifies the resource, distinguishing it from mutation siblings like add_item and put_proposal.

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?

Explicitly instructs to call before proposing changes, explains why (to avoid re-suggesting dismissed items), and identifies it as the only way to know what was deleted or rejected.

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

All What Matters toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool targets a distinct resource (items, focus, rules, proposals) with clear action verbs, and the descriptions explicitly delineate when to use add_item vs put_proposal and warn against using manage_focus/manage_rule outside conversation, leaving no ambiguity.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern (add_item, complete_item, get_document, manage_focus, manage_rule, put_proposal), with verbs conveying the action and nouns the target.

Tool Count5/5

Six tools is well-scoped for this server: core item operations (add, complete, read), auxiliary resource management (focus, rules), and a proposal mechanism. Each tool has a distinct, non-redundant purpose.

Completeness3/5

The surface covers item creation, status changes, and reads, plus focus and rule management, but lacks direct item deletion or content editing; dismissal is mentioned in get_document but no tool performs it, requiring workarounds via proposals.

Resources