Skip to main content
Glama
Sign In
Devbook MCP Server

Devbook MCP Server

by leouofa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

devbook_list_projects

List and search Devbook prompt projects with prompt counts and pagination so you can find and inspect workspaces by name or description.

Instructions

List and search prompt projects / workspaces in Devbook with prompt count metrics and pagination

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

Input Schema

NameRequiredDescriptionDefault
qNoSearch query to filter projects by name or description
limitNoNumber of projects to return (default 50, max 100)
offsetNoPagination offset (default 0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/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 burden. It does add real behavioral context by disclosing that results include prompt count metrics and that pagination is supported, but it omits whether the operation is read-only, how results are ordered by default, whether a total count is returned, and any auth or rate-limit constraints.

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?

A single front-loaded sentence with no filler, and the capability plus return content are stated up front. The only minor friction is the 'prompt projects / workspaces' slash construction, which leaves the resource naming slightly ambiguous.

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

Completeness3/5

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

For a three-optional-parameter list tool with no annotations and no output schema, the description covers the essentials of filtering and pagination. However, with no output schema, it should say more about the response shape than just 'prompt count metrics' — for example, whether a total or cursor is included.

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?

Schema description coverage is 100%, so all three parameters (q, limit, offset) are already fully documented in the schema. The description only restates the search and pagination concepts at a high level, adding no syntax, matching behavior, or default-value detail beyond the 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 names a specific verb pair (list, search) and a specific resource (prompt projects / workspaces in Devbook), plus what is returned (prompt count metrics). It implicitly separates itself from devbook_get_project by being a collection query, though it does not explicitly name any sibling.

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 implied rather than stated: 'list and search' suggests browsing/filtering, and the presence of a search parameter hints at keyword lookup. There is no explicit guidance on when to use this instead of devbook_get_project for a single record, nor any prerequisites or exclusions.

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

Deploy Server

Other Tools