Skip to main content
Glama
Sign In

Scribase

by com.scribase
OverviewDiscussionsAdmin

List branches

branches.list
Read-onlyIdempotent

Branches of a project with kind, status, parent and expiry. Production is protected. Scope: branches:read.

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": "branches.list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum items to return (default 50)
cursorNoOpaque cursor from a previous page's next_cursor
project_idNoProject id. Optional: defaults to the project created or used last in this session, or the only one.
organization_idNoOrganization id. Optional: defaults to the token's organization, or the only one you belong to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world, non-destructive behavior. The description adds useful context beyond them: production is protected, the call requires branches:read scope, and it names the fields returned. It still omits pagination or output-format details, but those are partly handled by the schema.

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 three short sentences, front-loaded with the resource and key facts. There is no filler or repetition, and every sentence contributes 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?

For a simple read-only list operation with full schema coverage and clear annotations, the description covers the resource, returned fields, protection status, and required auth scope. The main remaining gap is sibling disambiguation, but the definition is otherwise sufficient.

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?

All four parameters have complete schema descriptions with defaults and meanings. The description mentions no parameter-specific behavior or defaults, so it does not add meaning beyond the schema; baseline 3 applies because schema coverage is 100%.

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 identifies the resource (branches of a project) and the fields surfaced (kind, status, parent, expiry), which is more than a restatement of the title. It does not clearly distinguish this tool from the sibling branch.list (singular) or explain when to choose one over the other, so it is clear but not fully differentiated.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, no prerequisites, and no named alternative for listing branches versus branch.list, branch.diff, or branch.register. The only usage-adjacent statement is the read scope, which is not routing guidance.

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

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