Skip to main content
Glama

Little Works

discover_capabilities

Map of what Discover can do for an AI: source people by skill, source projects/learn, cook recipes, listen to music, buy materials, book services, find doctors, search, make community requests. Call this first.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

With no annotations, the description carries the full disclosure burden. It implies a safe, informational read (a 'map of what Discover can do'), but it never states the return shape, whether the output is a static catalog or reflects live data, or whether results vary by caller. For a zero-parameter orientation tool the risk is low, so this is adequate rather than strong.

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?

It is a single compact sentence plus a short imperative, with no filler. The one structural weakness is that the most actionable instruction, 'Call this first,' is buried at the end of a long capability list rather than front-loaded.

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?

There are no parameters and no output schema, so the description is the only source of truth about what an agent gets back, and it does not describe the return value or its structure. The domain coverage list partly compensates by telling the agent what capabilities exist to be discovered, but a first-call orientation tool would benefit from a line about what the map contains.

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 no parameters, so there is nothing for the description to disambiguate. The baseline for a zero-parameter schema applies, and no misleading parameter language is introduced.

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 frames the tool as a capability map for the Discover surface and enumerates the domains it covers (sourcing people, projects, recipes, music, materials, services, doctors, search, community requests). That is enough for an agent to tell it apart from the operational siblings like discover_search or buy_material, which each do one of those things. It stops short of a crisp verb+resource statement, but the intent is unmistakable.

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?

'Call this first' is an explicit, unambiguous usage directive that tells the agent to invoke this before the domain tools. What is missing is any when-not condition or a note about whether re-calling is needed after the first use, but the primary routing guidance is present and clear.

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