Skip to main content
Glama

store_info

Shows which Relate file Strata reads and writes, including path, size, last change, sites, and interpretive-edit count so agents can verify storage context.

Instructions

Which Relate file this server reads and writes (path, size, last change), why that file, the sites in it, and how many interpretive edits it holds.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "store_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full load; it does disclose the specific fields returned (path, size, last change, sites, edit count), which is useful. However, it says the server 'reads and writes' that file without clarifying that this particular tool is a read-only inspection with no arguments and no side effects, leaving a small risk of misreading it as a mutating operation.

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?

The whole definition is one front-loaded sentence that lists the returned contents without padding. The parenthetical 'why that file' is slightly vague, but no sentence is wasted.

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?

With zero parameters and an output schema present, the description only needs to convey what class of information the tool surfaces, which it does. Nothing required to invoke it is missing, though the absence of usage routing against the other introspection siblings is a residual gap.

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?

The tool takes zero parameters and the schema is empty at 100% coverage, so there is nothing for the description to disambiguate. Baseline 4 applies for a parameterless tool.

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 concrete resource and enumerates its contents (file path, size, last change, sites, interpretive edit count), so the agent can tell it is a storage-status tool. It lacks an explicit verb like 'report' or 'return', and it draws no boundary against the closest siblings (describe, overview, history, provenance).

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?

No when-to-use guidance, no exclusions, and none of the neighboring introspection tools (describe, overview, provenance, history) are named as alternatives. The agent must infer that this is the tool to reach for when it needs to know which file backs the data.

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