KeelTools AI Directory

Get KeelTools entry details

get_entry

Get structured details for one entry by type and slug: tagline, pricing model, features, use cases, pros, cons and FAQ. Use search_directory first to find the slug.

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": {
      "type": "<type>",
      "slug": "<slug>"
    },
    "name": "get_entry"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	Entry slug, e.g. 'aider' or 'code-review-assistant'
`type`	Yes	Entry type: tool, skill or prompt

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 17, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. The verb 'Get' and the field list imply a safe, read-only lookup and partially compensate for the absent output schema, but nothing is said about auth requirements, rate limits, or what happens when the slug is not found.

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 sentences with no filler. The purpose and returned fields come first, and the prerequisite (search first) is placed after, which is the right ordering for a lookup tool.

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 no output schema, the description usefully enumerates the payload (tagline, pricing, features, use cases, pros, cons, FAQ), which is the key missing structured information. It is essentially complete for a simple two-parameter lookup, though it says nothing about failure modes for an invalid slug.

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 100% and the enum on 'type' is documented in the schema, so both parameters are already fully specified there. The phrase 'by type and slug' restates the key without adding format, casing, or validation detail beyond the schema's own examples.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get structured details for one entry') and pins down the lookup key ('by type and slug'). It also enumerates the returned fields, which clearly separates it from the sibling search_directory, whose job is discovery rather than retrieval.

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?

Explicitly names the alternative and the ordering constraint: 'Use search_directory first to find the slug.' That gives the agent a concrete workflow. It stops short of stating when-not to use it (e.g., behavior for an unknown slug), so it is strong but not exhaustive.

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

All KeelTools AI Directory tools Inspect

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

Need Help?