Skip to main content
Glama

List Playground agent approvals

playground_approvals_list
Read-onlyIdempotent

Read pending proposals, exact scopes, expiry, and price ceilings for the current user and project.

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": {
      "projectId": "<projectId>"
    },
    "name": "playground_approvals_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYesID of the Playground project chosen for this task; obtain it from project creation, an explicit project link or current context.
conversationIdNoConversation ID for filtering or continuing the associated agent work.

Output Schema

NameRequiredDescriptionDefault
approvalsYes

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 a safe read (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the safety profile is covered. The description adds real behavioral context beyond that: results are limited to *pending* items and scoped to the current user and project, and it signals the payload includes scopes, expiry, and price ceilings. It stops short of mentioning ordering, pagination, or whether expired approvals appear.

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?

A single front-loaded sentence with no filler; each noun (pending, scopes, expiry, price ceilings, current user, project) conveys distinct information about the call.

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 annotations, an output schema, and 100% schema coverage, the description only needs to frame the call, which it does by stating scope and the kind of records returned. Minor gaps remain around result ordering/pagination and whether non-pending approvals are ever included, but nothing essential for correct invocation is missing.

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%, and both parameters carry UUID formats, patterns, and descriptions, so the schema does the heavy lifting. The description's 'for the current user and project' loosely reinforces the projectId scoping but adds nothing about conversationId or how it filters results.

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 gives a specific verb ('Read') and enumerates the resource content (pending proposals, scopes, expiry, price ceilings), so an agent knows this is a read of approval records scoped to the current user and project. It does not explicitly name the counterpart action tool (playground_approval_decide), so sibling differentiation is only implicit via 'pending' vs. decide.

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 rather than stated: 'pending proposals' suggests calling this before deciding on an approval. There is no explicit when-to-use/when-not statement, no mention of playground_approval_decide as the follow-up, and no note about whether the tool should be re-polled to refresh pending state.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.