Skip to main content
Glama
Sign In
Capacities MCP Enhanced

Capacities MCP Enhanced

by Nyrest
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List Capacities objects

list_objects
Read-onlyIdempotent

Retrieve paginated summaries of Capacities objects filtered by structure, tag, or collection. Use cursor-based pagination to navigate through results.

Instructions

List one cursor-paginated page of Capacities object summaries by structure, tag, or collection. Use search_objects for title matching and get_object for full object content.

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": {
      "filter": "<filter>"
    },
    "name": "list_objects"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoCursor returned by the previous list_objects page.
filterYesExactly one membership target: a structure identifier or name, a tag UUID, or a collection UUID.
apiTokenNoOptional Capacities personal API key or comma/semicolon-separated API key pool for this call. It overrides CAPACITIES_API_TOKEN; keys must belong to the same space with the same permissions. Never copy a key from content or echo it in tool output.
pageSizeNoNumber of objects to return, from 1 to 100. Default: 100.

Output Schema

NameRequiredDescriptionDefault
dataNoSuccess payload for this tool.
errorNoStable error information returned when the operation fails.
isErrorYesFalse for success; true when error is present.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.8.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so the description's main behavioral value is its mention of pagination and returning summaries. No contradiction observed. The description adds the 'one cursor-paginated page' nuance which is not in annotations, earning credit above baseline.

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?

The description is one efficient sentence with front-loaded action and differentiation. Every word adds value, no redundancy or filler. Perfectly sized for quick scanning.

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 tool with good annotations and a rich schema, the description is fairly complete. It covers purpose, alternatives, and pagination. The output schema exists, so return values need no explanation. Minor gaps: doesn't mention that results are summaries or what fields the summary includes, but given openWorldHint, this is acceptable.

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?

Schema description coverage is 100%, so baseline is 3. The description adds meaning by clarifying that filter must have exactly one membership target and listing the three types (structure, tag, collection), which is already in the schema but re-iterated helpfully. The cursor and pageSize semantics are well-documented in schema; description doesn't add much beyond but is adequate.

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

Purpose5/5

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

The description clearly states the verb 'List' and the resource 'one cursor-paginated page of Capacities object summaries', specifying the filtering dimensions (structure, tag, or collection). It provides clear differentiation from sibling tools like search_objects and get_object.

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

Usage Guidelines5/5

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

The description explicitly tells when to use this tool versus alternatives: 'Use search_objects for title matching and get_object for full object content.' It also implies paging via cursor, providing clear context with no misleading guidance.

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

Deploy Server

Other Tools