Skip to main content
Glama
Sign In
Devbook MCP Server

Devbook MCP Server

by leouofa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

devbook_get_project

Retrieve full details for a Devbook project by its unique ID, including the prompt list index and project metadata.

Instructions

Get full project details including its prompt list index and metadata

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "devbook_get_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesUnique identifier of the project

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. "Get" implies a read-only, non-mutating call, and it names two payload components (prompt list index and metadata), but it says nothing about what happens when the id is unknown (error vs empty), whether full details include attachments or prompt bodies, or how large the response may be.

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; the salient scope word ("full") appears before the supporting detail. It is slightly under-informative rather than padded, which is the right failure mode for a one-parameter tool.

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 simple one-parameter read with no output schema, the description must at least characterize the returned payload. "Prompt list index and metadata" gestures at the shape but leaves key content (does it include prompts, attachments, timestamps?) undefined, and error behavior is unaddressed.

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?

Only one parameter exists and schema coverage is 100%, with the schema itself documenting "Unique identifier of the project" plus an exclusiveMinimum constraint. The description adds no format, sourcing, or lookup guidance beyond that, so the baseline of 3 applies.

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?

"Get full project details" pairs a specific verb with a specific resource and a scope qualifier ("full"), so the agent knows this is a single-record retrieval by identifier rather than a listing. It never names devbook_list_projects or devbook_get_prompt as contrasts, so differentiation is inferred from the noun rather than stated.

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: needing a project's full details (including prompt list index) suggests this over devbook_list_projects, but the description states no when-to-use rule, no exclusions, and no prerequisite that a valid project id must already exist. An agent can infer the intent from the verb, but nothing routes it explicitly.

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