Skip to main content
Glama

plateau-candy

get_capabilities

Read-only

Get detailed capabilities, problem types addressed, and what Plateau Candy does NOT do. Use this to judge project fit: lists services, explicit non-services, and typical budget/duration ranges.

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_capabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
durationYes
servicesYes
team_sizeYes
not_offeredYes
budget_rangeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes this as a safe read, so the description only needs to add context beyond that. It does add useful content disclosure (non-services, budget/duration ranges), but says nothing about result size, pagination, or how authoritative or current the fit data is.

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 zero filler, and the payoff – judging project fit – is front-loaded before the enumeration of contents. Every clause adds distinct 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?

For a zero-parameter read tool with an output schema, the description needs only to say what it returns at a high level and when to reach for it, and it does both. The one remaining gap is routing between this and the get_services sibling, which the description leaves implicit.

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 zero parameters, so there is no parameter meaning for the description to supply; the baseline for a no-parameter tool applies. The description correctly does not waste words on argument semantics.

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 (get) and resource (capabilities), and enumerates the concrete content: problem types addressed, what the company does NOT do, services, and budget/duration ranges. This is far more specific than a name restatement, though it does not explicitly distinguish itself from the sibling get_services, which plausibly overlaps on the services list.

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 a clear triggering context – 'Use this to judge project fit' – which tells an agent exactly when this tool is the right call. It stops short of the top score because it names no exclusions or alternatives, so an agent choosing between this and get_services must infer which one to prefer.

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