Skip to main content
Glama
Sign In
PerMark

PerMark

by EdelmarSchneider
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_notes

Read-only

List notes a person shared with AI agents, including title and age, so you can review available context before working.

Instructions

Notes the person shared with agents (note, age, title).

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_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.7.0
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and locality are covered. The description adds that results carry note, age, and title fields, but says nothing about ordering, completeness, or whether all shared notes are returned at once.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with no waste, and the scope qualifier plus returned fields arrive immediately. The fragment phrasing ('Notes the person shared with agents') is slightly awkward but costs nothing in length.

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?

With no output schema and no parameters, the description does the minimum by naming the returned fields (note, age, title). It leaves open whether results are paginated, ordered, or truncated, and 'age' is undefined, which matters for a zero-argument listing tool.

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

Parameters4/5

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

The tool takes zero parameters, so the schema requires no compensation; baseline is 4. The description does not need to explain any argument, and the parenthetical field list is a bonus rather than a substitute for parameter documentation.

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

Purpose3/5

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

The phrase 'Notes the person shared with agents' identifies the resource and a scoping qualifier (shared with agents) plus the returned fields (note, age, title), so an agent can tell it is a listing tool distinct from list_unread or list_tags. However, 'Notes' is not a clear verb and there is no explicit statement of what the tool does versus read_note or search.

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

Usage Guidelines2/5

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

The description gives no when-to-use guidance, no exclusions, and never names alternatives such as list_unread, search, or read_note despite six list/read siblings in the toolset. The only implied usage is 'person shared with agents,' which is scope, not a selection rule.

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