Skip to main content
Glama
Sign In
Otohiroi MCP

Otohiroi MCP

by koyomivanp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_packs

List sound packs registered with add_pack and check whether Freesound downloads are enabled, so you can confirm available audio sources before searching or fetching sounds into your game project.

Instructions

Packs registered with add_pack, and whether Freesound downloads are enabled.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/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 burden. It does disclose one useful behavioral fact beyond the schema: the result includes whether Freesound downloads are enabled. It does not confirm the operation is a read-only listing with no side effects, nor does it describe ordering, emptiness, or output shape.

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?

A single short, front-loaded sentence with no filler. It is a sentence fragment rather than a complete statement, which slightly weakens readability, but nothing is wasted.

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 zero-parameter, zero-annotation tool with no output schema, the description should at least sketch what comes back. It names two return elements (pack list, Freesound-enabled flag) but leaves the shape, ordering and empty-case behavior unstated, which is a clear gap for a listing tool.

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, which is the baseline-4 case; there are no arguments whose meaning needs explaining. The description neither misleads about inputs nor adds unnecessary parameter commentary.

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 fragment names a specific resource (packs) and ties it to the sibling that creates them (add_pack), so an agent can tell it retrieves the registry of added packs. However, it never states an explicit verb ('list' is only in the name) and the second clause about Freesound downloads reads as a return-value note rather than part of the tool's purpose.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no routing to alternatives such as search_sounds or add_pack. The connection to add_pack is descriptive of data provenance, not an instruction about when the agent should call this tool.

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