Skip to main content
Glama

myco_sense

Search the Myco substrate for a keyword substring to verify ground truth before asserting a fact. Returns file path, line number, and snippet for each match.

Instructions

Perform a keyword substring search across the substrate's markdown + yaml surface and return ranked hits with file path, line number, and snippet. This is the R3 SENSE-BEFORE-ASSERT mechanism: before asserting a substrate fact from training memory, the agent calls this to check ground truth from the substrate itself (R3 of the Hard Contract).

Use this before making any claim about what the substrate contains — e.g. "the substrate says X" should always be preceded by a sense call that returned a hit for X. Fast (no embedding, no LLM, no network) — this is a literal substring scan over notes/, docs/, _canon.yaml, and MYCO.md. For broader semantic search, compose multiple sense calls with different keyword synonyms rather than expanding the query.

Side effects: none. Pure read. Does not touch .myco/state/ or any cache.

Returns: { exit_code, query, scope, hits: [ { path, line, snippet } ] }. hits is ordered by path then line number; snippet is the full matching line trimmed to reasonable width. Empty hits is a successful call with no matches — agent should treat "absence of hit" as "fact not in substrate" per R3.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesLiteral substring to search for. Case-insensitive. No regex, no glob — pass 'error' not 'err.*' (regex-in-query is treated as literal). For multi-term search, call sense multiple times and union results. Whitespace-only queries return empty hits.
project_dirNoAbsolute path of the workspace / project whose Myco substrate this call targets. Overrides auto-discovery. When omitted, Myco resolves via MCP roots/list, then MYCO_PROJECT_DIR, then cwd — the substrate_pulse field in every response echoes which source answered.
Behavior5/5

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

With no annotations provided, the description fully carries the burden of behavioral disclosure. It states side effects are none, it is a pure read, does not touch .myco/state/ or any cache, and details the return format. It also explains that an empty hits array represents a successful call with no matches, which is important for the agent's decision-making.

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?

The description is well-structured with clear sections for purpose, usage, side effects, and returns. It is front-loaded with the key action and resource, and every sentence provides essential information without redundancy. Despite moderate length, it is efficient and earns its length.

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 the tool has only two parameters, no output schema, and a large set of sibling tools, the description is remarkably complete. It covers purpose, usage context, behavioral traits, parameter details, return format, edge cases (empty hits), and interaction patterns (composing multiple calls). No gaps remain for the agent to infer.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100%, the description adds significant value beyond the schema: it explains that query is case-insensitive, no regex or glob, and whitespace-only queries return empty hits. For project_dir, it details the resolution order (MCP roots/list, MYCO_PROJECT_DIR, cwd) and that the response echoes which source answered. This greatly enhances parameter understanding.

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 performs a keyword substring search across the substrate's markdown and yaml surface, returning ranked hits with file path, line number, and snippet. It distinguishes itself from siblings by referencing the R3 SENSE-BEFORE-ASSERT mechanism, making its purpose unique and clear.

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?

The description explicitly guides the agent to use this tool before making claims about substrate content, and recommends composing multiple calls with synonyms for broader semantic search instead of expanding the query. It clarifies that the tool is a literal substring scan with no embedding, LLM, or network, providing clear when-to-use and alternatives.

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/Battam1111/Myco'

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