Skip to main content
Glama

list_projects

Read-only

The team's projects by name, each with its id, slug, colour, status pages and apps. A key held to one page gets only the project that page is in.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real behavioral context beyond them: which fields come back and that a page-restricted key silently filters the result set to one project — an important non-obvious scoping behavior. It does not mention pagination or ordering guarantees, keeping it short of 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?

Two short sentences, front-loaded with the resource and return shape, then the key-scope caveat. The opening is a sentence fragment ("The team's projects by name...") but nothing is padded or redundant.

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?

With no parameters, no output schema, and annotations covering safety, the description covers what matters: what collection is returned, which fields each item carries, and how auth scope affects results. Only pagination/ordering behavior is unaddressed, which is a minor gap for a zero-argument list tool.

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 per the baseline the description needs only to not mislead about inputs; it correctly implies no filtering or paging arguments are offered. The note about key scope is the closest thing to an input-affecting factor and is handled accurately.

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 states the resource ("the team's projects by name") and enumerates the returned fields (id, slug, colour, status pages, apps), so the agent knows this is a read that returns a project collection. It is not a clean verb+resource phrasing and does not differentiate itself from get_project, which weakens it slightly.

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 only implied by the collection framing; there is no statement of when to call this instead of get_project or any other sibling, and no exclusions. The one genuinely useful usage signal is the note that a page-scoped key yields only that page's project, which tells the agent when results will be narrowed.

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