Skip to main content
Glama

Echoo public catalog

Search Echoo skills

search_echoo_skills
Read-onlyIdempotent

Find published skills using generic task keywords such as tone or translate. Returns source links, not generated writing.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_echoo_skills"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of skills returned.
queryYesGeneric task keywords. Empty lists skills.

Output Schema

NameRequiredDescriptionDefault
countYes
skillsYes
sourceUrlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds that results are source links rather than generated writing, which usefully sets expectations, but says nothing about result ordering, empty-result behavior, or paging beyond the documented limit.

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 short sentences with no filler: the first states what is found and how to phrase the query, the second states the return nature. Front-loaded and every clause carries information.

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 rich annotations, an output schema, and fully documented parameters, the description only needs to establish scope and query style, which it does. A note on empty-query or no-results behavior would close the last gap, though the schema hints at the empty case.

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%, so baseline is 3, but the description adds genuine meaning by exemplifying the kind of query string expected ('tone', 'translate'), reinforcing the schema's 'generic task keywords'. The limit parameter is left to the schema, which is acceptable.

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?

Uses a specific verb+resource pair ('Find published skills') and adds a scope qualifier that only published skills are searchable. The second sentence ('Returns source links, not generated writing') further pins down what the tool is, distinguishing it from a content-generation or single-skill-fetch tool. It stops short of naming the sibling get_echoo_skill explicitly, so not a 5.

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?

Gives input-style guidance ('generic task keywords such as tone or translate'), which implicitly tells the agent when this tool fits, but never states when to prefer it over get_echoo_skill or when not to use it. Usage is inferable rather than explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources