Skip to main content
Glama
Sign In

Scribase

by com.scribase
OverviewDiscussionsAdmin

List edge functions

functions.list
Read-onlyIdempotent

Edge functions deployed to a branch. Scope: functions: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": "functions.list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum items to return (default 50)
branchNoBranch (environment) id. Optional: defaults to `production`.
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

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description's real contribution is the required auth scope ('functions:read'), which is useful operational context not present in annotations. It says nothing about pagination defaults or result shape, but the schema carries those.

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

Conciseness4/5

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

Two short fragments with zero waste, and the scope constraint is cleanly separated and front-loaded. It is terse to the point of being terse rather than informative, but nothing is redundant.

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

Completeness3/5

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

With five optional parameters, no output schema, and cursor-based pagination, the definition is only minimally complete: it never states that results are paginated or what a returned function contains. The auth scope plus rich schema descriptions compensate partially, but an agent gets no picture of the return payload.

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%, so all five parameters (limit, branch, cursor, project_id, organization_id) are documented with defaults. The phrase 'deployed to a branch' subtly reinforces that branch is the primary scoping dimension, but the description adds no format or semantics beyond the schema.

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 is a noun phrase ('Edge functions deployed to a branch') rather than a verb+resource statement, so the 'list' action comes entirely from the name and title. It does add the resource scope (deployed functions, branch-scoped), which helps distinguish it from functions.deploy and functions.logs, but the purpose is only implied.

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 guidance on when to use this tool versus siblings such as functions.deploy or functions.logs, and no preconditions stated. An agent must infer that this is the read/inventory counterpart to deploy.

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