Skip to main content
Glama
delimit-ai

delimit

Official
by delimit-ai
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

Delimit Resource List

delimit_resource_list
Read-onlyIdempotent

Enumerate resources such as repos, pull requests, issues, and workflow runs from a connected data-plane system via a driver. Use to list items; for a specific item use the get tool.

Instructions

List resources from a connected data-plane system.

When to use: to enumerate items via a driver — repos, PRs, issues, workflow runs. When NOT to use: to fetch a specific item (use delimit_resource_get) or inventory drivers (delimit_resource_drivers).

Sibling contrast: delimit_resource_drivers lists drivers; delimit_resource_get fetches one item; this lists items.

Side effects: read-only network calls via the chosen driver. Calls ai.data_plane.get_driver and the driver's list_* method.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orgNoOrganization filter for repos.
repoNo"owner/name" — required for workflow listing.
limitNoMax results. Default 10.
stateNoPR/issue state — "open" (default), "closed", "all".open
driverNoDriver key. Default "github".github
resourceNoOne of "repos", "pull_requests", "issues", "workflows". Required.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed6 schema fields changedv4.7.9
    • changedInput schema / properties / driver / description
      Previous value: -"The data plane driver to use (default: github)."New value: +"Driver key. Default \"github\"."
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of results."New value: +"Max results. Default 10."
    • changedInput schema / properties / org / description
      Previous value: -"Organization filter (for repos)."New value: +"Organization filter for repos."
    • changedInput schema / properties / repo / description
      Previous value: -"Repository in owner/name format (required for workflows)."New value: +"\"owner/name\" — required for workflow listing."
    • changedInput schema / properties / resource / description
      Previous value: -"The resource type to list (repos, pull_requests, issues, workflows)."New value: +"One of \"repos\", \"pull_requests\", \"issues\", \"workflows\". Required."
    • changedInput schema / properties / state / description
      Previous value: -"State filter for PRs/issues (open, closed, all)."New value: +"PR/issue state — \"open\" (default), \"closed\", \"all\"."
  2. Addedv4.5.5

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses the side effect of read-only network calls, names the internal calls to ai.data_plane.get_driver and the driver's list_* method, and confirms no destructive behavior. This gives an agent a clear model of what executing the tool involves.

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 compact and well-structured: a one-sentence purpose followed by tightly scoped sections for usage, contrast, and side effects. Every sentence earns its place with no filler.

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

Completeness5/5

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

The description is self-sufficient for selection and invocation: purpose, alternatives, side effects, and internal behavior are all covered. Parameter details and return shape are delegated to the input/output schemas, which is appropriate given the schema coverage.

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?

The schema already documents all six parameters with descriptions, so the description does not need to restate parameter semantics. It adds general context about driver-based enumeration but no parameter-specific detail beyond the schema. The baseline of 3 applies because schema coverage is complete.

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 resources from a connected data-plane system' and clarifies that it enumerates items like repos, PRs, issues, and workflow runs. It distinguishes itself from peers by naming delimit_resource_get and delimit_resource_drivers as different operations.

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 'When to use' and 'When NOT to use' guidance, including named alternatives. This leaves no ambiguity about when to choose this tool over delimit_resource_get or delimit_resource_drivers.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/delimit-ai/delimit-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server