Skip to main content
Glama

bx_projects_list

Read-onlyIdempotent

List saved projects with pagination using limit and offset, returning isolated project records without source text or model calls.

Instructions

分页列出已保存项目。 / List isolated projects without source text. Paginated; no model call.

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": "bx_projects_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo

Output Schema

NameRequiredDescriptionDefault
dataYes
kindYes
productYes
api_versionYes
business_decisionYes
execution_authorizationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0-rc.9-linux.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds two genuinely non-obvious traits: results are paginated, and no model/LLM call is made (so it is inexpensive and deterministic). It stops short of stating ordering or whether an empty page signals the end of results.

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?

Three short clauses, front-loaded with the core action, and every clause carries information: what is listed, what is excluded, and the pagination/cost profile. The bilingual restatement is duplicated content but is compact and does not bury the key facts.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety semantics; the description fills the remaining gap by noting that source text is excluded and that results are paged. For a two-parameter, side-effect-free listing tool this is nearly complete, with only page-size defaults and ordering left unstated.

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

Parameters3/5

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

The input schema has 0% description coverage, so the description carries the burden; 'paginated' at least signals that limit/offset control result windows. It adds nothing about the maximum page size of 50, the default limit, or whether offset is a record count versus a page number, all of which an agent must infer from the schema constraints alone.

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+resource ('List isolated projects') and adds a scoping qualifier ('without source text'), which tells the agent this returns project metadata rather than full project bodies. It distinguishes itself from a single-record fetch by being explicitly a listing, but it never names the sibling (bx_project_get) that would be the alternative for one project.

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?

'Paginated; no model call' implies this is a cheap enumeration call suitable for discovery before fetching details, which is useful implicit guidance. However, there is no explicit statement of when to prefer this over bx_project_get or bx_project_create, and no note on when to stop paging, so the usage decision is inferred rather than stated.

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