Skip to main content
Glama

doer_get_project

Retrieves full details of a Doer project workspace, including its todo lists and metadata, by project ID.

Instructions

Get full details of a Doer project workspace, including its associated todo lists 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": "doer_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.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden; it does disclose that the response bundles todo lists and metadata alongside project fields, which is useful knowledge for an agent. However, it says nothing about read-only/safety characteristics beyond the implicit "Get", nor about failure behavior for an invalid or nonexistent id.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler, and the informative part about the return contents comes immediately after the action. Nothing in it could be cut without losing meaning.

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?

This is a simple read tool with one well-documented parameter and no output schema, so the description's summary of the returned payload is close to sufficient. What remains missing is guidance on where the id comes from and how errors are surfaced, which are modest gaps for a tool of this complexity.

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?

The input schema has 100% description coverage for the single required parameter ("Unique identifier of the project"), so the schema already does the explanatory work. The description adds no format, range, or sourcing detail beyond the schema, which matches the baseline for full coverage.

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 a specific verb and resource ("Get full details of a Doer project workspace") and adds scope detail about what the payload includes ("associated todo lists and metadata"). It does not explicitly contrast with siblings like doer_list_projects or doer_get_todo_list, but the phrase "full details" distinguishes a single-record fetch from a list operation.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives such as doer_list_projects (to discover an id) or doer_get_todo_list (for a specific list). It also doesn't state prerequisites, such as needing a valid project id obtained elsewhere. Usage is only implied by the verb "Get".

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