Skip to main content
Glama

Upravio public knowledge

Popis javnih tema

list_capabilities
Read-onlyIdempotent

Popis funkcionalnosti, AI obrade, pohrane, pomoći i uvjeta uvođenja; ne prikazuje podatke korisničkih organizacija.

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": "list_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?

Annotations already declare readOnly, idempotent, closed-world and non-destructive behavior, so safety is covered. The description's one contribution beyond that is the disclosure that customer organization data is deliberately excluded from the result, which sets a useful expectation about what comes back, but nothing is said about result shape, size, or localization of the output.

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?

A single sentence with no filler, front-loading the subject matter and ending on the most decision-relevant clause (the exclusion of customer data). The comma-separated topic list is slightly loose but every item arguably signals content the agent can expect.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter, read-only listing with rich annotations and no output schema, the description supplies everything needed to select and call it: the subject matter, the scope boundary, and the absence of arguments. No further detail would materially change how an agent invokes it.

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 semantics to explain and the baseline of 4 applies. The schema is empty and fully consistent with the description's framing as a fixed, argument-free information listing.

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 names the resource being listed (functionalities, AI processing, storage, help, onboarding conditions) with the listing verb implied by the name, and adds a negative scope statement ('does not show customer organization data'). It is clear what the tool returns, though the enumerated topics are broad and it never explicitly contrasts itself with get_knowledge or search_knowledge.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent can infer this is for learning what the platform offers rather than for retrieving customer content, thanks to the closing exclusion. There is no explicit 'use this when...' instruction and no named alternative for the customer-data case, leaving the agent to infer that get_knowledge or search_knowledge cover that ground.

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