Skip to main content
Glama
Sign In
gramps-evidence-mcp

gramps-evidence-mcp

by ianderso
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

list_research_tasks

Read-only

List research tasks in Gramps Web's Tasks view by title, status, priority, tags, attributes, and description; filter by status, tag, or attributes.

Instructions

List the research tasks in Gramps Web's Tasks view: title, status, priority, tags, attributes and description.

Ordered as the view orders them: Open, In Progress, Blocked, Done. Not background jobs (list_jobs). A private task is a redacted stub.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
tagNoOnly tasks also carrying this tag.
statusNoOnly these states, e.g. ['Open', 'In Progress'].
attributesNoOnly tasks with these attribute values, ignoring case; an empty value matches any value, e.g. {'Request-Custodian': ''}.
include_privateNoShow living people and private records in full. Only when the user asks for them; they are withheld by default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.3.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds a non-obvious behavioral detail the annotations cannot carry: 'A private task is a redacted stub,' which tells the agent results can be partially hidden, plus the view-ordering guarantee. It does not discuss result size or pagination.

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?

Three short sentences, zero filler. The scope/fields statement comes first, then ordering, then the sibling exclusion and privacy caveat – well front-loaded and every sentence carries information.

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?

With no output schema, the description compensates by naming the returned fields, and all four parameters are covered by the schema. The only gap is that nothing is said about result volume/pagination for a tool that lists a whole view, though the filtering params mitigate that.

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 description coverage is 100% – tag, status, attributes and include_private are each documented in the schema with examples and defaults. The description adds no filtering syntax or semantics of its own; the indirect link between 'private task is a redacted stub' and include_private is only implied. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('List') and resource ('research tasks') and enumerates the fields returned ('title, status, priority, tags, attributes and description'), so an agent knows exactly what comes back. It also distinguishes itself from the similarly-named sibling: 'Not background jobs (list_jobs).'

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?

Explicitly rules out the most likely confusion point by naming list_jobs, and notes the ordering follows the Tasks view (Open, In Progress, Blocked, Done). It gives clear context but no positive 'use this when...' statement or guidance on combining the filters.

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