Skip to main content
Glama
Sign In

KeeSpecs

by xyz.keespecs
OverviewDiscussionsAdmin

get_ecosystem

Read-only

The KeeSpecs directory: Keeta's own products and apps, plus community entries seeded from their own public pages. Community entries are unclaimed or self-claimed, not verified by KeeSpecs. Not a ranking. Free.

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

Input Schema

NameRequiredDescriptionDefault
idNoOptional community entry id, e.g. velocity

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint. The description adds useful behavioral context: community entries are unclaimed or self-claimed, not verified, not a ranking, and free. It does not explain pagination or response format, but the trustworthiness caveats go beyond structured fields.

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 description is short and front-loaded with the directory identity and key caveats. It uses fragments rather than full sentences, but no sentence is wasted.

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?

For a simple read-only directory tool with one optional parameter and no output schema, the description supplies the essential context about data provenance and trust. It could clarify what happens when an id is supplied, but the schema already covers that parameter.

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 single optional id parameter is documented in the schema. The description does not add meaning about the id parameter or explain behavior when it is provided versus omitted, so the schema does all the work.

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 clearly identifies the resource as the KeeSpecs directory containing Keeta products/apps and community entries. It does not state an explicit retrieval verb or distinguish this tool from the sibling get_directory tool, but the data scope is unambiguous.

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?

The description explains the directory's nature and trust caveats but gives no guidance on when to use this tool versus alternatives such as get_directory. There are no explicit inclusion or exclusion conditions.

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

All KeeSpecs toolsInspect
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