Skip to main content
Glama

List karaokes

list_karaokes
Read-only

List the connected account's Quick projects to find work to continue in this chat.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNo

Output Schema

NameRequiredDescriptionDefault
errorNo
projectsNo
next_cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds only the account-scoping detail and says nothing about pagination behavior, ordering, result size, or how the cursor interacts with limit, all of which matter for a list tool with a cursor parameter.

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

Conciseness3/5

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

One short sentence with no filler, so it is tight, but the brevity comes at the cost of substance rather than from efficient phrasing. The useful scoping clause is present but there is nothing about the pagination parameters.

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

Completeness2/5

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

An output schema exists, so return values need not be spelled out, but for a cursor-paginated list tool the description should still explain paging and result semantics. With 0% parameter coverage and a mutation-free read tool whose annotations carry the rest, the definition is under-informed for its complexity.

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%: limit and cursor carry types, defaults and bounds but no explanatory text, and the description does not compensate at all. An agent gets no statement of what limit caps or how cursor tokens are obtained and reused across calls.

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 description uses a clear verb ("List") and names a scope ("the connected account's Quick projects"), but "Quick projects" does not obviously map to the tool name list_karaokes or to the karaoke-centric siblings, so an agent may hesitate over what is actually returned. The added clause about finding work to continue in this chat hints at intent, but the resource naming is ambiguous.

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?

"To find work to continue in this chat" is a light usage hint that implies discovery/browsing rather than fetching a known item, which nudges an agent away from get_karaoke. However, no sibling is named and no explicit when-not condition is given, so the guidance stays implied rather than stated.

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