Skip to main content
Glama

geezorg_browse

Browse archive paths to list files and folders for Amharic dictionaries, abbreviations, plurals, homonyms, gemination lists, parallel Amharic-English news, and Sabaean/Falasi glossaries.

Instructions

List the files and folders at a path of the archive, for example 'amharic/dictionaries'. The archive also holds abbreviations, plurals, homonyms, gemination lists, parallel Amharic-English news and Sabaean/Falasi glossaries that have no dedicated tool.

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

Input Schema

NameRequiredDescriptionDefault
pathNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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 disclosure burden. It makes clear this is a read-only listing of archive paths and scopes what the archive contains, but says nothing about recursion depth, what happens on an invalid path, or whether an empty path means the archive root.

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 purpose is front-loaded in the first clause and the example path follows immediately. The second sentence is somewhat tangential but earns its place by telling the agent what else lives in the archive and why no dedicated tools exist for it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter listing tool with an output schema already documenting return values, the definition covers purpose and archive scope adequately. It still leaves the agent guessing about the default root path and whether the listing is recursive or single-level.

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?

Schema description coverage is 0% and the single `path` parameter has no description, so the description must compensate. It partially does by showing the expected format via the example 'amharic/dictionaries' (slash-separated, no leading slash), but never explains that the default empty string means the root listing.

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 opens with a specific verb+resource ('List the files and folders at a path of the archive') and supplies a concrete example path ('amharic/dictionaries'), so an agent immediately knows this is a directory-listing tool. It does not name or contrast any sibling such as geezorg_read_file, so differentiation from alternatives is left implicit.

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

Usage Guidelines3/5

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

Usage is only implied: the second sentence notes the archive contains abbreviations, plurals, homonyms, gemination lists, parallel news and Sabaean/Falasi glossaries 'that have no dedicated tool', which hints that browsing is the way to reach those materials. There is no explicit when-to-use / when-not-to-use statement and no pointer to geezorg_read_file or geezorg_corpus_search.

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