Skip to main content
Glama
zzallirog

weighted-compact

by zzallirog
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

substrate_info

Check which components are built (pairs, sessions, importance signals) to avoid unnecessary setup costs for other tools.

Instructions

Report what's built and what isn't — cheap diagnostic.

    Returns a dict with pair_count, session_count, has_importance,
    has_rem_decay, rem_decay_ref_iso (ISO timestamp of the last
    REM pass), and signals_present (names of the importance mixture
    components). Includes path of the substrate workdir.

    Use this on connect to know which other tools will succeed
    without paying their setup cost first. Always returns a dict
    even when nothing is built.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A4.8/5.0
Behavior5/5

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

With no annotations, the description fully describes behavior: returns a dict with specific fields, includes path, and is a cheap read. No side effects mentioned; appropriate for a diagnostic 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?

Compact with three sentences, front-loaded purpose. Minor redundancy but overall efficient.

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?

Given output schema exists, description adds usage context and lists key fields, making it complete for a zero-param tool.

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?

No parameters in schema, so no param info needed. Description adds value by explaining what the output contains, going beyond the schema's empty input.

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 reports 'what's built and what isn't' as a cheap diagnostic, and lists specific return fields. It distinguishes from sibling tools (compact_session, search_pairs) by being a diagnostic info tool.

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?

Explicit guidance: 'Use this on connect to know which other tools will succeed without paying their setup cost first.' Also notes it always returns a dict even when nothing is built.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zzallirog/weighted-compact'

If you have feedback or need assistance with the MCP directory API, please join our Discord server