Skip to main content
Glama
baggybin

ask-fable

by baggybin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

context_read

Read-onlyIdempotent

Retrieve stored context blobs by key, or list all available keys with metadata to discover what can be referenced. Read-only inspection for reusing context without re-pasting.

Instructions

Read the shared context bus: pass key to get a stored blob back (value plus its size, age and description; not_found if unset), or OMIT key to LIST every stored key (size/age/description, never the full value). Read-only — use it to inspect a blob, or to discover what is already available to reference via context_ref before re-pasting.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoKey to read back. Omit to LIST every stored key (with its size, age and description) — the discovery call before re-pasting context.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.18.0
    • changedInput schema / properties / key / description
      Previous value: -"Key to read back."New value: +"Key to read back. Omit to LIST every stored key (with its size, age and description) — the discovery call before re-pasting context."
    • changedInput schema / required
      Previous value: -[
-  "key"
-]New value: +[]
  2. First observedv0.12.0

TDQS

A4.5/5.0
Behavior5/5

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

The description discloses exact behavior beyond annotations: `not_found` when a key is unset, metadata returned with each blob, and the important distinction that list mode never returns full values. This is especially valuable because there is no output schema.

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 well-structured sentences deliver the mode distinction, return format, missing-key behavior, read-only guarantee, and a pointer to `context_ref`. No filler; information is front-loaded and every clause earns its place.

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?

Despite having no output schema, the description fully covers both invocation forms, the shape of returned data, the missing-key case, the read-only nature, and how the tool fits into the context-ref workflow. An agent has everything needed to invoke and interpret results correctly.

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?

The input schema already documents `key` and the omit-to-list behavior at 100% coverage, so the baseline applies. The description adds return-behavior context (size, age, description, not_found) but no new parameter constraints or format details, so it doesn't substantially exceed schema coverage.

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?

States a specific verb ('Read') and resource ('shared context bus'), then precisely distinguishes the two invocation modes: pass `key` to get a blob, or omit `key` to list stored keys. It also mentions `context_ref` as the referencing counterpart, which helps separate it from related tools.

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

Usage Guidelines4/5

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

Explicitly gives two concrete use cases: inspect a single blob, or discover available keys before re-pasting via `context_ref`. It doesn't enumerate exclusions or compare against sibling tools, but the usage context is clear enough for an agent to decide when to call it.

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