Skip to main content
Glama
Sign In
Samuraizer

Samuraizer

by UladzKha
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_meetings

Retrieve processed meetings in reverse chronological order. Set a limit to control the number of results.

Instructions

List all processed meetings, sorted newest first. Optionally limit results.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of meetings to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.6

TDQS

A4/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds useful behavior: it lists only processed meetings, sorts newest first, and supports an optional limit, but it does not mention output shape, pagination, default behavior when limit is omitted, or any performance considerations.

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 front-loaded sentence that conveys the verb, resource, ordering, and optional parameter without any filler. Every word 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?

For a simple read-only list operation with one optional parameter and no output schema, the essential call context is present: scope, ordering, and limit. It would be slightly more complete if it defined what 'processed' means or noted the default result size, but these are minor gaps for this low-complexity tool.

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 description coverage is 100% and the only parameter, 'limit', is already documented as 'Maximum number of meetings to return.' The description's phrase 'Optionally limit results' adds no new semantic meaning beyond what the schema already provides, so the baseline of 3 applies.

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 states a specific verb ('List'), a precise resource ('all processed meetings'), and the ordering ('newest first'). It differentiates itself from siblings like search_meetings and get_meeting by focusing on the complete processed set rather than filtering or a single record.

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

Usage Guidelines4/5

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

The description clearly implies this tool is for retrieving the full list of processed meetings, with an optional limit. However, it does not explicitly name alternatives or state when not to use it, such as using search_meetings for filtered queries or get_meeting for a specific meeting.

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