Skip to main content
Glama
Sign In
hearthsmith

hearthsmith

by Eyalm321
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

hearthsmith_tasks_list

List tasks filtered by state (open, done, blocked, delegated, all) and project ID or name to quickly find relevant work items.

Instructions

List tasks. state: open | done | blocked | delegated | all. project filters by hyperpanes project id/name.

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": "hearthsmith_tasks_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNoopen
projectNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

With no annotations provided, the description must carry the behavioral burden. 'List' implies a read-only operation, and the state values are enumerated, but the description does not disclose pagination, sorting, or any side effects. It is adequate but not rich.

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 compact, front-loaded with the core action ('List tasks'), and immediately clarifies the key parameters. Every sentence earns its place with no filler.

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 has an output schema, so return details are not needed. The description covers the essential filtering options and states the allowed state values. Minor omissions like pagination or default behavior are acceptable for a simple list tool, so it is nearly complete.

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

Parameters5/5

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

Despite 0% schema description coverage, the description fully explains both parameters: state lists all allowed values (open, done, blocked, delegated, all) and project filters by hyperpanes project id/name. This adds significant meaning beyond the bare schema.

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?

The description begins with 'List tasks,' a specific verb and resource, and clearly distinguishes this from siblings like hearthsmith_tasks_done, hearthsmith_tasks_add, etc. It is unambiguous that this tool retrieves a collection of tasks, not modifies them.

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

Usage Guidelines3/5

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

The description provides filter options (state, project) and implies this is the general listing tool, but it does not explicitly state when to prefer this over siblings such as hearthsmith_tasks_done or hearthsmith_nags_recent. It gives context but no exclusions or alternatives.

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