Skip to main content
Glama
Sign In
Longhand

Longhand

by Wynelson94
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

find_episodes

Find problem-fix episodes by project, time range, keyword, or fix status. Retrieve raw data instead of narrative.

Instructions

Structured search for problem→fix episodes. Filters: project_ids, time range, keyword, has_fix. Returns raw episode rows. Use this when you already know the project or want data instead of narrative.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 20)
sinceNoISO timestamp
untilNoISO timestamp
has_fixNo
keywordNo
project_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

No annotations provided. Description indicates a read-like search operation ('Structured search', 'Returns raw episode rows') but lacks details on performance, rate limits, or side effects.

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?

Two concise sentences: first states purpose and lists filters, second provides usage guidance and output type. No redundant 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?

Covers primary usage and output type. Lacks details on default behavior without filters and pagination beyond 'limit' parameter, but sufficient for basic understanding.

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 50% (only 'since', 'until', 'limit' described). The description lists additional filters ('project_ids', 'keyword', 'has_fix') but does not explain their semantics, e.g., what fields 'keyword' searches.

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 clearly states 'Structured search for problem→fix episodes' with specific filters, distinguishing it from siblings like 'get_episode' and 'search'.

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

Usage Guidelines5/5

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

Explicit guidance: 'Use this when you already know the project or want data instead of narrative.' This context helps the agent choose among siblings.

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