Skip to main content
Glama
Sign In
delegations-mcp

delegations-mcp

by kaijfox
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

list_delegations

Retrieve and refresh available delegation prompts for orchestrating tasks between primary and specialized agents in project workflows.

Instructions

List all available delegations. Also refreshes the registry from disk.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses a behavioral trait: 'refreshes the registry from disk', indicating a side effect that might impact performance or data freshness. However, it lacks details on permissions, rate limits, or what 'refreshes' entails (e.g., overwrites cache).

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?

The description is concise with two clear sentences. However, the second sentence about refreshing the registry could be better integrated or explained, slightly reducing efficiency. It's front-loaded with the primary purpose.

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?

Given 0 parameters, 100% schema coverage, and an output schema exists, the description is reasonably complete. It covers the main action and a side effect. However, for a tool with behavioral implications (refreshing), more context on when and why to use it would enhance completeness.

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?

There are 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description doesn't add param info, but with no params, this is acceptable. Baseline is 4 as per rules for 0 parameters.

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 clearly states the verb 'list' and resource 'delegations', making the purpose specific. However, it doesn't explicitly distinguish this from sibling tools like 'get_delegation' (which likely retrieves a single delegation) or 'run_delegation' (which likely executes one).

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 guidance is provided on when to use this tool versus alternatives like 'get_delegation' or 'run_delegation'. The description mentions 'refreshes the registry from disk', which hints at a side effect but doesn't clarify if this is a primary use case or when it's appropriate compared to other listing methods.

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