Skip to main content
Glama
ohmstead-mcp

ohmstead-mcp

Official

List projects

list_projects
Read-only

Lists your Ohmstead projects newest first, using your personal workspace by default or a specified team name or id to view its accessible projects.

Instructions

The user's Ohmstead projects, newest first. Personal workspace by default; pass team (name or id, see whoami) for that team's projects you can see.

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

Input Schema

NameRequiredDescriptionDefault
teamNoTeam or class name or id. Omit for your personal projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real context beyond that: result ordering (newest first), the default scope, and an access limitation ("projects you can see"). It says nothing about pagination or result size limits, which matters for a list tool and keeps this at a 3.

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 compact clauses with zero filler; the scope and default are front-loaded before the optional parameter. Nothing is repeated or padded.

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

Completeness4/5

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

For a single-optional-parameter read tool with no output schema, the description covers scope, default, ordering, and where to get a team id. A brief note on whether the result is paginated or capped would make it fully complete.

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 says "Team or class name or id. Omit for your personal projects," so the description mostly restates it. The only added value is the cross-reference to whoami for obtaining a team id, which the schema does not provide.

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?

The description opens with a specific verb and resource ("The user's Ohmstead projects") and adds an ordering guarantee ("newest first"), so an agent knows exactly what it returns. It is distinguishable from get_project by being a listing, though it never names that sibling explicitly.

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?

It states the default behavior (personal workspace) and the condition that changes it (pass team for that team's projects), which is the key routing decision for this tool. It stops short of explicit when-not guidance or naming get_project as the alternative for a single project.

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