Skip to main content
Glama
Sign In

Pineprompt

by com.pineprompt
OverviewDiscussionsAdmin

List Projects Tool

list-projects-tool
Read-onlyIdempotent

List the projects within an organization, newest first. Returns up to 50 per page; follow nextCursor to fetch additional pages. Optionally pass include to load the parent organization.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "organization_id": "<organization_id>"
    },
    "name": "list-projects-tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoOpaque pagination cursor. Omit on the first call; pass the `nextCursor` value from the previous response to fetch the next page.
includeNoOptional comma-separated related resources to include in the response. Whitelisted: `organization`.
organization_idYesThe numeric id of the organization whose projects should be listed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the description only needs to add operational detail. It does: result ordering (newest first), a hard page-size cap of 50, and the cursor-based continuation mechanism, all of which an agent needs to page correctly and none of which appear in the annotations.

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?

Three short sentences, front-loading the resource and ordering before the pagination mechanics. Every clause carries actionable information with no filler.

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?

With only three parameters, no output schema, and full annotation coverage, the description is close to sufficient: it describes the return shape (a paged list, newest first, capped at 50) and how to continue. What a project record contains and any error behavior are unstated, a minor gap for a simple read tool.

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 each parameter is already documented, setting the baseline at 3. The description restates the cursor-following pattern and notes that `include` loads the parent organization, but adds no format or constraint detail beyond what the schema already says.

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?

"List the projects within an organization, newest first" gives a specific verb, resource, scope, and sort order, which separates it from the other list-* siblings by resource type. It does not name a specific alternative tool, but the resource scope is unambiguous.

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 resource scope and the pagination instruction ("follow `nextCursor` to fetch additional pages") tells the agent how to iterate. However, there is no explicit when-to-use/when-not guidance and no mention of siblings such as create-project-tool or list-organizations-tool.

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

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