OrgLines

List functions

list_functions

Read-only

List the caller's sandboxed user functions in their active workspace (newest first). Read-only. Each item carries id, name, description, version, status (enabled/disabled), exposed_as_tool and this month's run fair-use usage. Only the caller's own functions are returned.

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

Input Schema

Name	Required	Description	Default
`limit`	No
`offset`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and non-destructive, so 'Read-only' is redundant, but the description adds genuine context: result ordering (newest first), the visibility boundary (caller's own functions only, active workspace), and the exact item shape including status, exposed_as_tool and monthly fair-use usage. It does not disclose pagination or result-count behavior.

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?

Three short sentences, front-loaded with scope and ordering, then the item shape. Dense and waste-free; 'Read-only' is the only line that merely restates an annotation.

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 no output schema, naming the returned fields is valuable and largely compensates there. However, a list tool with limit/offset parameters and no pagination guidance leaves a real operational gap, so the definition is adequate but incomplete.

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% and the description never mentions the limit or offset parameters, their bounds, defaults, or whether results are paginated. With two undocumented parameters, the description leaves the caller without any paging guidance.

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?

States a specific verb and resource ('List the caller's sandboxed user functions') plus a precise scope ('in their active workspace') and ordering ('newest first'). The scope constraint 'Only the caller's own functions are returned' distinguishes it from any workspace-wide listing tool.

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?

Usage is implied by the scope statement (list your own functions in the current workspace), but the description never says when to prefer this over alternatives or what the caller should do for other scopes. No exclusions or prerequisites are given.

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

All OrgLines tools Inspect

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

Need Help?