list_projectsList the curated, public projects with stack, status, last-active date, and test/CI signals, plus anonymized portfolio-wide aggregates. Optionally filter by status.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max projects | |
| status | No | Filter by status, e.g. "active" or "archived" |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, so the description adds value by specifying the returned content (anonymized aggregates) and optional filtering. No contradictions; the behavioral traits are transparent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence that efficiently conveys the purpose, included fields, and optional filtering. Every word adds value, and the most important information is front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description covers the main elements (what is listed, aggregates, filtering) but omits details like pagination behavior, default limit, or ordering. However, given the simplicity of the tool and presence of annotations, it is reasonably complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so baseline is 3. The description does not add new meaning beyond the schema: it repeats that status filtering is optional but does not explain limit or provide examples. No additional parameter semantics are introduced.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool lists curated public projects with specific fields (stack, status, last-active date, test/CI signals) and includes portfolio-wide aggregates. The verb 'List' and resource 'projects' are specific, and it distinguishes from siblings like list_corpus and list_repo_profiles which target different resources.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for retrieving a filtered list of projects but does not explicitly state when to use this tool over siblings like search or list_corpus. No 'when to use' or 'when not to use' guidance is provided, but the context is clear enough for basic understanding.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct resource or action: documents, operant results, profile, repo profiles, corpus listing, project listing, repo profile listing, and full-text search. No overlap in functionality.
Most tools follow a verb_noun pattern (get_, list_, search), with 'search' being a lone verb but still clear. Minor inconsistency: 'list_corpus' uses singular 'corpus' but lists multiple items.
8 tools is well-scoped for a portfolio site, covering profile, documents, projects, repo profiles, and search without being excessive or insufficient.
Covers core read-only functionalities: profile, documents, projects, repo profiles, and search. Missing a dedicated 'get_project' tool, but list_projects provides sufficient detail for the portfolio context.