Skip to main content
Glama

Ellimist

Find an Ellimist skill (free)

find_skill
Read-only

Describe what you need in plain words (e.g. 'is this wallet sanctioned', 'earthquakes near Tokyo'). Returns matching tools with price, input schema and an example call. Free.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false; the description usefully adds what comes back (price, input schema, example call) and that the call is free, which is real context an agent cannot get from the annotations. It omits result-count behavior, default limit, and any rate or cost caveats on downstream tools, so it is informative but not complete.

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 plus a parenthetical of examples, front-loaded with the primary instruction. Every element earns its place; the examples do real work in showing the expected query style.

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?

There is no output schema, and the description correctly covers the return shape and the free pricing, which is what an agent most needs here. The only gap is the undocumented 'limit' parameter, minor for a 2-parameter discovery tool.

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%, so the description carries the burden. It compensates well for 'query' by explaining plain-language phrasing and giving examples, but never mentions 'limit' (1-20, optional), leaving its purpose and default entirely undocumented.

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?

States a specific verb and resource: takes a plain-language need and returns matching tools with price, input schema and an example call. That is enough to distinguish it from the sibling data_/quantum_/exchange_ tools, which all perform work rather than discovery, though the description never explicitly frames itself as the discovery entry point to those siblings.

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?

Gives concrete when-to-use framing via two examples ('is this wallet sanctioned', 'earthquakes near Tokyo') that show the query should be a task in natural language rather than a keyword or tool name. No explicit exclusions or statement of when a sibling should be called directly instead, which keeps it out of 5 territory.

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