Skip to main content
Glama

Scalix Cloud

by world.scalix
OverviewDiscussionsAdmin

scalix_project_list

Read-onlyIdempotent

List every project in an organization, with each project's ID, name, and slug. Use this to resolve a project ID before calling project-scoped tools. org_id is optional: omit it to list the projects of the organization the API key belongs to (resolved via GET /v1/me). Needs an admin API key: organization admin scope is never delegated to a connected app, so this tool fails on an OAuth connection.

Input Schema

NameRequiredDescriptionDefault
org_idNoOrganization ID whose projects to list. Optional — defaults to the API key's own organization.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / org_id / description
      Previous value: -"Organization ID whose projects to list"New value: +"Organization ID whose projects to list. Optional — defaults to the API key's own organization."
    • changedInput schema / required
      Previous value: -[
-  "org_id"
-]New value: +[]
  2. Changed1 schema field changed
    • changedInput schema / properties / org_id / description
      Previous value: -"Organization ID"New value: +"Organization ID whose projects to list"
  3. First observed

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 admin API key requirement, the fact that org-admin scope is never delegated to connected apps, and that it fails on OAuth connections. It also explains the org resolution path (GET /v1/me). This is well past 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?

Four short sentences with no waste, front-loaded with purpose then usage then auth constraint. Every sentence 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?

For a single-optional-param read tool, the description covers purpose, return contents, usage routing, and the critical auth caveat. Nothing an agent needs to call it correctly 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 coverage is 100% and the schema already documents org_id's meaning and default. The description reinforces the default behavior and adds the resolution mechanism, but adds little parameter-level semantics the schema doesn't already carry.

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?

States a specific verb and resource ('List every project in an organization') and enumerates the returned fields (ID, name, slug). It is trivially distinguishable from the write-oriented sibling scalix_project_create.

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?

Explicitly says 'Use this to resolve a project ID before calling project-scoped tools', giving the exact precondition for use. It also states when to omit org_id and when the tool will fail (OAuth connections), covering the when/when-not cases.

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

All Scalix Cloud 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