Skip to main content
Glama
Sign In

OTP

by io.github.david-steel
OverviewDiscussionsAdmin

List quarterly rocks

list_rocks
Read-only

List quarterly rocks for the authenticated organization. Filter by quarter (e.g. '2026-Q2') or owner_external_id. Each rock carries status: on_track, off_track, completed or archived. Read status, not the on_track flag: a completed rock can still carry on_track false from before it was finished. Archived rocks are left out unless include_archived is true.

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

Input Schema

NameRequiredDescriptionDefault
quarterNoQuarter filter, e.g. '2026-Q2'
on_trackNoOnly open rocks that are on track (true) or off track (false); completed and archived rocks are excluded
include_archivedNoAlso return archived rocks. Default false.
owner_external_idNoFilter to one owner

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only and non-destructive behavior, so the description adds important context beyond them: status values, the distinction between status and the on_track flag, and the default exclusion of archived rocks. It does not cover pagination or return ordering, which keeps it from a 5.

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 appropriately sized and front-loaded: organization scope, filters, status semantics, and archived behavior all appear in a tight sequence. Every sentence carries useful information.

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?

Given the read-only annotations and no output schema, the description provides enough context to call the tool correctly, including status semantics and archived behavior. It could be slightly more complete with pagination or default quarter behavior, but the main gaps are minor.

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 coverage is 100%, so the schema already documents all four parameters, including the on_track parameter. The description reinforces quarter, owner_external_id, and include_archived but adds limited meaning beyond the structured schema for parameter usage.

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 and resource: list quarterly rocks, scoped to the authenticated organization. It is clearly distinct from mutation siblings such as add_rock and update_rock, and from unrelated list_* tools.

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?

It gives clear filtering usage for quarter and owner_external_id, and states that archived rocks are excluded unless include_archived is true. It does not explicitly name when to use this versus alternatives, but the listing context is clear.

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

All OTP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources