Skip to main content
Glama

shiply

by now.shiply
OverviewDiscussionsAdmin

List my client-intake projects

list_projects
Read-only

List the dev's customer-intake projects (newest first). Optional filters: status (draft|intake_open|brief_ready|brief_failed|archived), q (case-insensitive match on label or customer email), limit (default 100). Use to triage what's in flight before opening a specific project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNocase-insensitive match on label or customer email
limitNomax projects to return (default 100)
statusNofilter by project status
clientIdNoonly projects filed under this client

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / clientId
      Added value: +{
+  "description": "only projects filed under this client",
+  "format": "uuid",
+  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+  "type": "string"
+}
  2. Changed4 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"max projects to return (default 100)"
    • addedInput schema / properties / q / description
      Added value: +"case-insensitive match on label or customer email"
    • addedInput schema / properties / status / description
      Added value: +"filter by project status"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "result": {}
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations provide readOnlyHint: true, so the description adds value by specifying ordering (newest first) and the scope (dev's projects). While the safety profile is already known, the description clarifies behavior beyond what annotations convey.

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 two sentences with no wasted words. It front-loads the core action and then provides filter details and usage guidance in the second sentence. Every part earns its place.

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?

Given the presence of an output schema and annotations covering safety, the description sufficiently explains what the tool does, its optional filters, and its typical use case. No critical information is missing for a list endpoint.

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 coverage is 100%, so each parameter already has a description. The tool description reiterates the optional filters and adds default value for limit, but this is minimal additional context. It groups parameters fluently, but does not add significant new meaning.

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 clearly states it lists the dev's customer-intake projects, newest first, which is a specific verb and resource. It distinguishes from siblings like 'get_project' and other 'list_*' tools by explicitly mentioning 'customer-intake' and providing usage context.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description says 'Use to triage what's in flight before opening a specific project,' giving clear when-to-use context. It does not explicitly mention when not to use or list alternatives, but the guidance is sufficient and implies that this is for overview purposes.

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

All shiply toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources