Skip to main content
Glama

list_agents

Lists jobs managed by this MCP server, returning conversation IDs and statuses while omitting request and response bodies.

Instructions

このMCPサーバーが所有するジョブと会話ID・状態を返す(依頼・応答本文は含まない)

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses the ownership scope of what gets listed and which fields come back, including the important exclusion of message bodies, but says nothing about ordering, pagination, whether finished or cancelled jobs are included, or that the call is side-effect free.

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?

One compact sentence, front-loaded with what the call returns, followed by the exclusions in parentheses. There is no filler and no redundant restatement of the tool name.

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 zero-parameter listing tool with no output schema and no annotations, the description covers scope and the shape of the return value, which is the main thing an agent needs. Gaps remain around ordering and pagination behavior, but they are minor at this complexity level.

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 the baseline is 4; there is no parameter semantic to add meaning beyond the schema. The description's account of the returned fields partially compensates for the absent output schema.

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 uses a specific verb-plus-resource ('returns jobs owned by this MCP server') and names the fields returned (conversation ID, status), plus an explicit negative scope: request/response bodies are excluded. That negative scope is what lets an agent tell it apart from get_agent. It falls short of a 5 because it never names a sibling or reconciles 'agents' in the tool name with 'jobs' in the description.

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?

There is no explicit when-to-use statement or exclusion; the guidance is only implied by the note that bodies are omitted, which suggests a lightweight listing/polling role versus a detail fetch. The agent can infer the use case but must do the work itself.

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