Skip to main content
Glama
Sign In
agent-postit

agent-postit

by gerelef
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

postit.read_lines

Read a specific line range from a sticky note by name and inclusive start/end line numbers, retrieving only the needed portion without loading the whole note.

Instructions

Read a 1-based inclusive line range from a postit body.

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": {
      "arg": "<arg>"
    },
    "name": "postit.read_lines"
  }
}

Input Schema

NameRequiredDescriptionDefault
argYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 full burden. It adds useful context about 1-based inclusive indexing, but it does not disclose behavior for invalid line numbers, missing postits, or edge cases like out-of-range start/end. The 'dir' parameter's effect on lookup is also unexplained.

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 immediately states the action and key constraint ('1-based inclusive'), with no filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is relatively simple, but the description leaves parameter semantics and error behavior unaddressed. The output schema exists, so return values are covered, but with no annotations and four parameters, a bit more context would improve completeness.

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?

Schema description coverage is 0%, and the description only clarifies that start and end are a 1-based inclusive range. It does not explain what 'name' refers to, what 'dir' does, or how they relate to locating the postit. This fails to compensate for the lack of schema-level descriptions.

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 the action ('Read'), the resource ('a postit body'), and the specific scope ('1-based inclusive line range'). This distinguishes it from siblings like postit.read (full content) and postit.read_section (sections).

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 implies usage when needing a specific line range, but it does not explicitly discuss when to use it versus alternatives like postit.read or postit.read_section. No exclusions or prerequisites are mentioned.

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