Skip to main content
Glama

mocop

get_capabilities

Read-only

Operations, tools and skills of an entity (paged). Filter by group, kind, method or text; view older versions or removed items.

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

Input Schema

NameRequiredDescriptionDefault
qNo
kindNo
slugYes
sortNo
groupNo
limitNo
methodNo
offsetNo
removedNo
versionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real value by disclosing pagination ("paged") and the ability to reach "older versions or removed items," which an agent would not otherwise assume from a read-only list tool. However, it does not say how removed items are excluded by default or whether paging is offset/limit based.

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 well-formed sentence with the resource statement front-loaded and the filtering options following after a semicolon. Little waste, though the parenthetical "(paged)" is terse enough to border on cryptic.

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

Completeness2/5

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

Ten parameters, zero schema descriptions, no enums, no output schema and no parameter detail in the description. For a tool this wide, the definition is not complete enough for an agent to call it confidently without trial and error.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 10 parameters, so the description carries the full burden and only partially meets it: it names group, kind, method, text (q), version and removed, but adds no meaning (no valid kind/method values, no group semantics) and leaves slug, sort, limit and offset entirely undiscussed. Naming a parameter is not the same as explaining it.

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

Purpose3/5

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

The description identifies the resource as the "operations, tools and skills of an entity" and implies a read/list operation, but never states a verb and never distinguishes this from the sibling search_capabilities, which the phrase "Filter by ... text" actively overlaps with. An agent can guess it is an entity-scoped listing, but only by inferring from the required slug.

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?

No when-to-use guidance, no exclusions, and no mention of search_capabilities or get_entity_versions, which look like the closest alternatives. The parenthetical "(paged)" and the version/removed hints imply some usage, but nothing tells the agent when this tool is the right choice over its siblings.

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