Skip to main content
Glama

List notes

list_notes
Read-onlyIdempotent

List educational notes (slug, title, description, tags, url). Education only, not financial advice.

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

Output Schema

NameRequiredDescriptionDefault
siteYes
countYes
notesYes
disclaimerYes
generated_atYes
schema_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "count": {
      +      "type": "integer"
      +    },
      +    "disclaimer": {
      +      "type": "string"
      +    },
      +    "generated_at": {
      +      "type": "string"
      +    },
      +    "notes": {
      +      "items": {
      +        "additionalProperties": true,
      +        "properties": {
      +          "attachments": {
      +            "items": {
      +              "additionalProperties": true,
      +              "properties": {
      +                "mime_type": {
      +                  "type": "string"
      +                },
      +                "size_in_bytes": {
      +                  "type": "integer"
      +                },
      +                "title": {
      +                  "type": "string"
      +                },
      +                "url": {
      +                  "type": "string"
      +                }
      +              },
      +              "required": [
      +                "title",
      +                "url",
      +                "mime_type"
      +              ],
      +              "type": "object"
      +            },
      +            "type": "array"
      +          },
      +          "description": {
      +            "type": "string"
      +          },
      +          "path": {
      +            "type": "string"
      +          },
      +          "publishedAt": {
      +            "type": "string"
      +          },
      +          "slug": {
      +            "type": "string"
      +          },
      +          "tags": {
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": "array"
      +          },
      +          "title": {
      +            "type": "string"
      +          },
      +          "url": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "slug",
      +          "title",
      +          "description",
      +          "tags",
      +          "publishedAt",
      +          "url",
      +          "path",
      +          "attachments"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "schema_version": {
      +      "type": "string"
      +    },
      +    "site": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "schema_version",
      +    "generated_at",
      +    "site",
      +    "disclaimer",
      +    "count",
      +    "notes"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world behavior, so safety is covered. The description adds domain context ('Education only, not financial advice') and the returned fields, but does not disclose ordering, completeness, or pagination behavior.

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 two short sentences with no padding: the purpose and returned fields are front-loaded, followed by a brief domain caveat. Every sentence earns its place.

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 zero parameters, a present output schema, and rich annotations, the invocation is simple and the description supplies the important domain scope. It omits whether all notes are returned and in what order, which is a minor gap for a list operation.

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?

This tool takes zero parameters, so there is no parameter semantics to explain and the baseline is 4. The description lists output fields rather than confusing them with inputs, and the empty schema is fully consistent with the definition.

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

Purpose4/5

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

The description states a specific verb and resource: 'List educational notes', and enumerates the fields returned (slug, title, description, tags, url). It does not explicitly distinguish this from sibling list/search tools, but the purpose is clear.

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?

Usage is only implied by the verb 'List'; there is no explicit guidance on when to use this versus alternatives like get_note or search_content. No when-not-to-use or prerequisite information is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources