Skip to main content
Glama

My projects

projects_list
Read-onlyIdempotent

Your own Barmaan projects that the team has published to you: code, title, status (planned, active, on_hold, completed, cancelled), type, real progress (from milestones or team-recorded; null when none recorded), dates, overdue flag and next milestone. Includes summary counts (KPIs) and facets. Filter by q (title/code), status, type; sort by updated, due or title; page with page and page_size. Empty means no project is linked to your account yet. Free text is wrapped as data.

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

Input Schema

NameRequiredDescriptionDefault
qNoSearch in title, summary and project code.
pageNo
sortNoupdated
typeNo
localeNo
statusNo
page_sizeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so safety is covered; the description adds genuinely new behavior: the exact returned fields, that 'real progress' comes from milestones or team records and is null when nothing is recorded, that KPI summary counts and facets are included, and that an empty result means no project is linked to the account. It also flags a security trait ('Free text is wrapped as data') that annotations cannot express. It stops short of pagination limits or any permission model, so a 4 rather than a 5.

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 definition is front-loaded with the resource and scope, then the return shape, then filtering and paging in a compact run of clauses with no filler. It is dense to the point of being a single long sentence chain, which slightly hurts scanability but wastes no words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description steps in to describe returned fields, derived progress semantics, KPI/facet summaries and the empty-result meaning, which is exactly what an agent needs to interpret results. Combined with filter/sort/paging guidance and annotations covering safety, nothing material for correct invocation is missing beyond the minor locale omission.

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 only 14% (only q is documented), so the description carries most of the load and does add meaning: it enumerates the status values, names the type and sort options, and explains page/page_size. Two gaps remain: the locale parameter is never mentioned, and q is described as searching 'title/code' while the schema says 'title, summary and project code'.

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 opening clause names a specific resource and scope: 'Your own Barmaan projects that the team has published to you', which tells an agent this is a personal, read-only listing rather than a generic project catalog such as list_projects. The verb is implied by the list-like field enumeration rather than stated as 'list', keeping it just short of a 5.

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?

Usage is conveyed indirectly through the filter/sort/page instructions ('Filter by q (title/code), status, type; sort by updated, due or title'), so an agent can infer how to narrow results. However, there is no explicit statement of when to prefer this over list_projects or other sibling listing tools, and no prerequisites or exclusions are given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources