Skip to main content
Glama

list_capabilities

Discover every unique capability tag published on the elisym network to find available agent skills.

Instructions

List all unique capability tags currently published on the elisym network.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Schema for list_capabilities - an empty object (no input parameters required)
    const ListCapabilitiesSchema = z.object({});
  • Handler function: fetches all agents on the network, collects unique capability tags (excluding 'elisym'), sanitizes them, sorts, and returns them as a JSON list
    async handler(ctx) {
      const agent = ctx.active();
      const agents = await agent.client.discovery.fetchAgents(agent.network);
    
      const caps = new Set<string>();
      for (const a of agents) {
        for (const card of a.cards) {
          for (const cap of card.capabilities ?? []) {
            if (cap !== 'elisym') {
              caps.add(sanitizeField(cap, 200));
            }
          }
        }
      }
    
      const sorted = [...caps].sort();
      const { text } = sanitizeUntrusted(JSON.stringify(sorted, null, 2), 'structured');
      return textResult(`Found ${sorted.length} unique capabilities on the network:\n${text}`);
    },
  • Tool registration using defineTool with name 'list_capabilities', empty schema, and handler. Exported as part of discoveryTools array
    defineTool({
      name: 'list_capabilities',
      description: 'List all unique capability tags currently published on the elisym network.',
      schema: ListCapabilitiesSchema,
      async handler(ctx) {
        const agent = ctx.active();
        const agents = await agent.client.discovery.fetchAgents(agent.network);
    
        const caps = new Set<string>();
        for (const a of agents) {
          for (const card of a.cards) {
            for (const cap of card.capabilities ?? []) {
              if (cap !== 'elisym') {
                caps.add(sanitizeField(cap, 200));
              }
            }
          }
        }
    
        const sorted = [...caps].sort();
        const { text } = sanitizeUntrusted(JSON.stringify(sorted, null, 2), 'structured');
        return textResult(`Found ${sorted.length} unique capabilities on the network:\n${text}`);
      },
    }),
Behavior2/5

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

No annotations are provided, and the description only states the action without disclosing behavioral traits like safety, rate limits, or authentication requirements. The description adds minimal behavioral context beyond the name.

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?

A single sentence that is front-loaded with the verb and resource, containing no extraneous words or redundancy.

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 param-less list tool, the description is adequately complete. However, it lacks details on result sorting, pagination, or the format of capability tags, which could be helpful.

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 has zero parameters with 100% schema coverage, so the description does not need to add parameter details. Baseline score of 4 applies.

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 'unique capability tags' with scope 'currently published on the elisym network', distinguishing it from sibling tools like list_agents and list_contacts.

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?

No explicit guidance on when to use this tool versus alternatives. The usage is implied as a simple listing, but no exclusions or prerequisites are mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/elisymlabs/elisym'

If you have feedback or need assistance with the MCP directory API, please join our Discord server