Skip to main content
Glama

busabase

by com.busabase
OverviewDiscussionsAdmin

List change requests, or count them per inbox tab

change_request_query
Read-only

List change requests, or count them per inbox tab

Keyset-paginated: page with the returned cursor rather than raising limit. Pass countsOnly for just the per-tab totals (review / changes / created / approved / merged / rejected) without fetching rows. To check whether a specific resource already has an unfinished change request, pass affectsNodeId with limit 1 instead of paging the whole space: an empty result is conclusive.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mineNoOnly change requests you submitted.
limitNoPage size; 100 max.
cursorNoOpaque cursor from the previous page.
statusNoFilter by status, e.g. `in_review`, `approved`, `merged`.
playbookNoOptional. The playbook you are following, as `kind:nodeId[:key]` from playbooks_search (e.g. `prompt:nod_123:log-visit`). Recorded on the change request so the person can see which playbook produced it.
countsOnlyNoReturn per-tab counts instead of rows.
affectsNodeIdNoOnly change requests affecting this node — matching the node directly, its Base, or any of the change request's operations. Not available on the counts variant, whose totals are always space-wide.
targetSpaceIdNoBusabase space id. Call auth_verify first and ask the user which space to use when more than one is returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / playbook
      Added value: +{
+  "description": "Optional. The playbook you are following, as `kind:nodeId[:key]` from playbooks_search (e.g. `prompt:nod_123:log-visit`). Recorded on the change request so the person can see which playbook produced it.",
+  "type": "string"
+}
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context: pagination behavior (cursor-based), the countsOnly mode, and the optimization hint for checking a specific resource. It clarifies that the counts variant is space-wide and that affectsNodeId is unavailable there, all beyond annotation coverage.

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?

Two concise paragraphs. The first line states the purpose, and the second paragraph delivers three clear usage directives. Every sentence provides actionable information with no fluff. The most important usage guidance is front-loaded.

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 tool's complexity (8 params, no output schema, multiple modes), the description covers key usage patterns well. It addresses pagination, counting, and existence checks. However, it doesn't describe the shape of the list response (e.g., what fields a row contains) or error handling. With no output schema, this is a minor gap, but the description is still sufficient for correct invocation.

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

Parameters5/5

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

Schema coverage is 100%, so all parameters are described in the schema. The description adds meaningful semantics: explains how to use cursor ('page with the returned cursor rather than raising limit'), clarifies countsOnly behavior, and provides the recommended pattern for affectsNodeId with limit 1. It also details the playbook format in the schema, so the description complements rather than repeats.

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 clearly states the tool lists change requests or counts them per inbox tab. It distinguishes from siblings like change_requests_get and change_requests_list_page by focusing on listing/counting rather than single-fetch or mutation operations. The title reinforces this dual purpose.

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

Usage Guidelines5/5

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

Provides explicit usage patterns: keyset pagination with cursor, countsOnly for per-tab totals, and affectsNodeId with limit 1 for existence checks. These are actionable guidelines that tell the agent exactly when and how to use this tool for different scenarios, even if it doesn't name sibling alternatives directly.

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

All busabase 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