Skip to main content
Glama
rwese
by rwese

read

Retrieve backlog items from the MCP Backlog Server to view work items, filter by status or priority, and access detailed content for tracking progress.

Instructions

Read-only access to backlog items - list and view backlog work items

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicNoTopic name to fetch a single backlog item with full content
statusNoStatus filter for list operation
priorityNoPriority filter for list operation
showAgeNoInclude age information (default: true)

Implementation Reference

  • Main execution handler for the 'read' tool. Handles listing all backlog items or fetching details for a specific topic, including age and staleness info.
    async function handleBacklogRead(args: any) {
      const { topic, showAge = true } = args;
      
      // If topic is provided, fetch single item
      if (topic) {
        const item = await getBacklogItem(topic);
        
        if (!item) {
          return `Backlog item not found: ${topic}`;
        }
        
        // Return full item details including description
        const result: any = {
          topic: item.topic,
          priority: item.priority,
          status: item.status,
          version: item.version,
          created: item.created,
          agent: item.agent,
          session: item.session,
          description: item.description,
          filepath: item.filepath
        };
        
        if (showAge) {
          result.age = formatBacklogAge(item.created);
          result.isStale = isBacklogStale(item.created);
        }
        
        return JSON.stringify(result, null, 2);
      }
      
      // Otherwise, list items
      return await listBacklogItems(args);
    }
  • Input schema definition for the 'read' tool, returned by ListTools handler.
    {
      name: "read",
      description: "Read-only access to backlog items - list and view backlog work items",
      inputSchema: {
        type: "object",
        properties: {
          topic: {
            type: "string",
            description: "Topic name to fetch a single backlog item with full content",
          },
          status: {
            type: "string",
            enum: ["new", "ready", "review", "done", "reopen", "wontfix"],
            description: "Status filter for list operation",
          },
          priority: {
            type: "string",
            enum: ["high", "medium", "low"],
            description: "Priority filter for list operation",
          },
          showAge: {
            type: "boolean",
            description: "Include age information (default: true)",
          },
        },
      },
    },
  • src/index.ts:828-830 (registration)
    Registration/dispatch point for the 'read' tool handler in the CallToolRequestSchema switch statement.
    case "read":
      result = await handleBacklogRead(request.params.arguments);
      break;
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While it states 'read-only access', it doesn't describe what 'list and view' operations actually return, whether there are pagination limits, authentication requirements, rate limits, or any other behavioral characteristics. The description is too minimal for a tool with 4 parameters and no output schema.

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?

The description is extremely concise at just 10 words, front-loaded with the key information ('read-only access to backlog items'), and every word earns its place. There's zero waste or redundancy in this minimal description.

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

Completeness2/5

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

For a tool with 4 parameters, no annotations, and no output schema, the description is insufficiently complete. It doesn't explain what 'list' vs 'view' operations mean, how they relate to the parameters, what the return format looks like, or any behavioral constraints. The description should provide more context given the lack of structured metadata.

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?

With 100% schema description coverage, the schema already documents all 4 parameters thoroughly. The description mentions 'list and view backlog work items' which aligns with the parameters, but adds no additional semantic context beyond what's already in the schema descriptions. The baseline of 3 is appropriate when the schema does the heavy lifting.

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 clearly states the tool's purpose as providing 'read-only access to backlog items' with specific operations 'list and view backlog work items'. It uses a specific verb ('read-only access') and resource ('backlog items'), but doesn't explicitly distinguish it from sibling tools like 'todo-read' or 'read' vs 'write' operations.

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?

The description provides no guidance on when to use this tool versus alternatives. With sibling tools like 'todo-read', 'write', 'done', and 'todo-done' available, there's no indication of when this specific 'read' tool is appropriate versus those other options.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rwese/mcp-backlog'

If you have feedback or need assistance with the MCP directory API, please join our Discord server