Skip to main content
Glama

clawbridge_projects

Lists registered Luban projects while excluding credential references, filesystem allowlists, and secrets from the response.

Instructions

List registered Luban projects. Credential references, filesystem allowlists, and secrets are never returned.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses a real behavioral trait beyond structured fields — that credential references, filesystem allowlists, and secrets are stripped from the response — which matters for an agent that may need those values elsewhere. It does not state pagination, ordering, or whether results can be empty, so the disclosure is partial.

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?

Two short sentences with zero filler. The core action comes first and the security caveat follows, which is the right ordering for a listing tool.

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

Completeness3/5

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

With no output schema and no annotations, the description is the only documentation, and it does not describe the shape of a returned project entry (fields, identifiers, count). For a trivial zero-param list call this is serviceable, but an agent cannot predict what a 'project' record contains.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so no parameter explanation is required; the baseline of 4 applies. The description correctly does not waste words restating an empty schema.

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?

States a specific verb plus resource: 'List registered Luban projects.' An agent immediately knows the object being retrieved. It does not distinguish itself from any sibling, though none of the listed siblings appear to be a competing project-listing tool, so the differentiation gap is minor.

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 only implied: an agent inferring it needs the set of registered projects will call this. There is no explicit when-to-use statement, no prerequisites (e.g., auth/registration requirement), and no mention of alternatives.

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