Skip to main content
Glama
yyy188
by yyy188

validate_setup

Checks all dependencies, configuration, and storage readiness. Optionally verifies Jama OAuth token and embedding endpoint with live probes.

Instructions

Validate all dependencies, configuration and storage.

Runs the offline pre-flight (packages + env vars + SQLite). When
``live=True`` it also probes the Jama OAuth token and the embedding
endpoint with a real request, so credentials can be verified without
running a full project init.

Args:
    live: if True, perform live connectivity probes against Jama and the
          embedding endpoint (slower; uses one Jama + one embedding call).

Returns:
    {"blocking","issues":[...],"dependencies","config_issues","storage",
     "live": {"jama","embedding"} | null, "hint"}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
liveNo
Behavior4/5

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

The description discloses that live=True makes real requests to Jama and embedding endpoints, and notes it is slower. Without annotations, this provides adequate transparency about side effects and behavior. It could mention potential rate limits or that offline mode has no side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a brief summary followed by detailed Args/Returns. It is somewhat verbose but all sentences add value. Key information is front-loaded.

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?

The description covers both offline and live modes, explains return values, and provides context for credential verification. It lacks details on error handling or the specific checks performed, but is sufficient for a validation tool without an output schema.

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

Parameters5/5

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

The description thoroughly explains the 'live' parameter, including its effect (live connectivity probes), performance implications (slower, uses one call each), and purpose (verify credentials). This fully compensates for the 0% schema description coverage.

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 the tool validates dependencies, configuration, and storage, with offline pre-flight and optional live probes. This uniquely distinguishes it from sibling tools like bootstrap_models or init_jama_project, which serve different purposes.

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 explains when to use live=True (to verify credentials without full project init) and distinguishes offline from live modes. However, it does not explicitly state when not to use this tool or suggest alternatives for other validation needs.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yyy188/jama-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server