Skip to main content
Glama
Sign In

Mycel

by com.mycelhq
OverviewDiscussionsAdmin

firm_files

List the firm's repository: a folder (path, default the root) or a search across it (q). The repo is how the firm works: practice/, rules/, clients//, gtm/ (icp.md, playbook.md, pipeline.md, deals.md), analytics/, site/.

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": "firm_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoSearch text.
pathNoA folder, e.g. 'gtm' or 'clients/harbor-bistro'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the behavioral burden. It makes the read-only listing/search mode and default root clear, but says nothing about permissions, recursion, whether q searches filenames or file contents, result limits, or return shape.

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 compact sentences, with the primary operation front-loaded and the repository layout packed into the second. There is little waste.

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?

For a two-parameter list/search tool with no output schema and no annotations, the description covers purpose, modes, default path, and key repository structure. The remaining gaps are behavioral details about search and returned results, which keeps it short of complete.

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?

Schema coverage is 100%, and the description adds useful semantics beyond it: path defaults to the repository root, q is a search across the repo, and the listed directory layout helps choose paths. It still leaves the path/q interaction and search scope unspecified.

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 states a specific verb and resource—'List the firm's repository'—and distinguishes a folder listing via path from a search via q. It does not name siblings such as read_firm_file, so sibling differentiation is implicit rather than explicit.

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?

It gives clear usage context: pass path to browse a folder, with root as the default, or pass q to search across the repo. It does not state when to prefer this over read_firm_file, what_the_firm_knows, or other siblings, nor any when-not conditions.

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

All Mycel toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources