Skip to main content
Glama

get_due_items

Retrieve items scheduled for review, including overdue items, to manage knowledge resurfacing and maintain information recall.

Instructions

Get items due for review (inbox items)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stateYes

Implementation Reference

  • MCP tool handler that invokes apiClient.getDueItems and returns formatted JSON response or error.
    async ({ state }) => {
      const result = await apiClient.getDueItems(state);
    
      if (result.error) {
        return {
          content: [{ type: 'text', text: result.error }],
          isError: true,
        };
      }
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(result.data, null, 2),
          },
        ],
      };
    },
  • Zod input schema defining optional includeOverdue boolean parameter.
    state: z.object({
      includeOverdue: z
        .boolean()
        .optional()
        .default(true)
        .describe('Include overdue items'),
    }),
  • src/nodes.ts:57-88 (registration)
    Registration of the 'get_due_items' tool on the MCP server using server.tool.
    server.tool(
      'get_due_items',
      'Get items due for review (inbox items)',
      {
        state: z.object({
          includeOverdue: z
            .boolean()
            .optional()
            .default(true)
            .describe('Include overdue items'),
        }),
      },
      async ({ state }) => {
        const result = await apiClient.getDueItems(state);
    
        if (result.error) {
          return {
            content: [{ type: 'text', text: result.error }],
            isError: true,
          };
        }
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(result.data, null, 2),
            },
          ],
        };
      },
    );
  • Helper method in API client that sends POST request to backend /mcp/due-items endpoint with parameters.
    async getDueItems(params: {
      includeOverdue?: boolean;
    }): Promise<ApiResponse<any>> {
      return this.request('/mcp/due-items', {
        method: 'POST',
        body: JSON.stringify(params),
      });
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool 'gets' items, implying a read-only operation, but doesn't specify if it requires authentication, has rate limits, returns paginated results, or what format the output takes. This is a significant gap for a tool with no annotation coverage.

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 and front-loaded, consisting of a single, clear sentence that directly states the tool's purpose. There is no wasted verbiage, making it efficient for quick understanding.

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?

Given the complexity (one parameter with nested structure), no annotations, and no output schema, the description is incomplete. It doesn't cover behavioral aspects like safety or performance, parameter usage, or output format, leaving the agent with insufficient information to use the tool effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 0%, with one parameter ('state') that includes a nested object property ('includeOverdue'). The description adds no information about parameters—it doesn't explain what 'state' means, how 'includeOverdue' affects results, or any other input details. With low schema coverage, the description fails to compensate, resulting in poor parameter documentation.

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 with a specific verb ('Get') and resource ('items due for review'), and clarifies these are 'inbox items'. However, it doesn't differentiate this tool from sibling tools like 'search_nodes' or 'snooze_node', which might also deal with items/nodes, so it doesn't reach the highest score.

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. It doesn't mention sibling tools like 'search_nodes' (which might search for items) or 'complete_node' (which might mark items as done), leaving the agent without context for tool selection.

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/code-atlantic/Resurgo-MCP'

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