Skip to main content
Glama

List projects

dosai_list_projects
Read-onlyIdempotent

List every DOS AI project the key's owner can access, with status and channel (whatsapp_way: qr or official). Start here to get project ids. A key scoped to one project returns just that project. Never write a dosai.pro address from memory: a link to a cabinet page comes only from dosai_get_cabinet_link.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered; the description adds real value beyond that by disclosing the access-scoping rule and the returned fields including whatsapp_way values. It does not mention ordering, empty-result behavior, or pagination, which keeps it short of a 5 for a listing tool.

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?

Three sentences, front-loaded with the core action and the "start here" routing, with no filler. The anti-hallucination URL warning is useful but slightly tangential for a list tool and reads as a guardrail better suited to the cabinet-link tool.

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 input parameters, no output schema, and full annotation coverage, the description supplies what an agent needs: what it returns (projects with status and channel), the access-scoping behavior, and the follow-up tool for links. It stops short of describing ordering or result shape, which is minor given the absence of an output schema.

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 schema has zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly focuses on output semantics instead of inventing parameter guidance.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("List every DOS AI project") plus the access scope ("the key's owner can access") and the fields surfaced (status and channel with whatsapp_way values qr/official). This is clearly distinguishable from sibling list_* tools, which cover conversations, deals, contacts, etc., rather than projects.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Start here to get project ids" gives an explicit entry-point rule, and the final sentence names a specific alternative (dosai_get_cabinet_link) for the case where a cabinet page link is needed. It also explains the key-scoped edge case (a single-project key returns just that project), so both when-to-use and what-to-expect are covered.

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