Skip to main content
Glama
Sign In
LeadAce

LeadAce

by aitit-inc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_suggestions

Retrieve saved suggestions for a project, including status, title, body, and timestamps. Filter by open, dismissed, or done to review and manage actionable insights.

Instructions

List persisted suggestions for a project: id, kind, dedupeKey, title, body, command, status (open/dismissed/done), timestamps. Optional status filter.

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": {
      "projectId": "<projectId>"
    },
    "name": "list_suggestions"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNoFilter by status
projectIdYesProject name or ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.54

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It describes a read operation ('List persisted suggestions') and indicates it returns all suggestions by default, with an optional filter. It doesn't mention pagination, ordering, or whether deleted suggestions are included, but it is a simple read tool.

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 a single sentence that is compact and front-loaded with the core purpose. It lists the fields and the optional filter with no wasted words.

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?

The tool is simple: two parameters, no output schema, and no nested objects. The description covers the purpose, fields, and filter. It is complete enough for an agent to know what to expect, though it could mention if there is a limit or ordering.

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 coverage is 100%: projectId and status are both described in the schema. The description adds that status filter is optional and lists the status values, but it doesn't add much beyond the schema. Baseline 3 is appropriate.

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 lists persisted suggestions for a project and enumerates the returned fields. It distinguishes itself from siblings like record_suggestion (which creates) and list_documents, though it doesn't explicitly name alternatives.

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

Usage Guidelines4/5

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

It indicates the optional status filter and implies it is for reading suggestions in a project context. However, it does not provide explicit when-to-use or when-not-to-use guidance versus other list tools, but the context is clear enough.

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