Skip to main content
Glama
Sign In
stripe-billing-ops-mcp

stripe-billing-ops-mcp

by r28ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

linear_projects_list

Read-onlyIdempotent

List projects in your workspace to view their status and progress. Filter by team, lead, state, or health to track delivery.

Instructions

List projects in the workspace, with their status and progress.

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": "linear_projects_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
variablesNoPaging and filtering.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, so safety profile is explicit. The description adds the workspace scoping and return fields (status, progress), which is useful context beyond annotations. But it omits pagination behavior despite a `first`/`after` paging contract, and doesn't note default result size.

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?

Single short sentence, front-loaded verb and resource. No waste.

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

Completeness2/5

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

For a list tool with a rich filter/paging schema and no output schema, the description is too thin: it doesn't mention paging, default page size, filtering capability, or archived handling, all of which an agent needs to call it effectively.

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 the schema fully documents paging, filtering, ordering, and archived-inclusion. The description adds nothing about variables, so baseline 3 applies.

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?

Clear verb+resource: 'List projects in the workspace' with the added scope of status and progress fields. Distinguishable from siblings (none are project-listing), though it doesn't explicitly differentiate itself from other list tools in the sibling set.

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?

No guidance on when to use this versus alternatives, no prerequisites, no mention of paging defaults. The description just states what it does.

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

Deploy Server

Other Tools