Skip to main content
Glama

RationalBloks

by io.github.rationalbloks

Get Project Info

get_project_info
Read-onlyIdempotent

Get detailed project info including deployment status and resource usage. DEPLOYMENT STATUS: Running (healthy), Pending (starting), CrashLoopBackOff (init container failed - usually schema format error), ImagePullBackOff (image build failed). TROUBLESHOOTING: If status is CrashLoopBackOff, the schema is likely in wrong format (nested 'fields' key or missing 'type' properties). Use get_schema to review current schema. If replicas show 0/2, the init container (migration runner) is failing. This is almost always a schema format issue.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesProject ID (UUID)

TDQS

A4.4/5.0
Behavior5/5

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

The description goes well beyond the annotations, which only indicate readOnly and idempotent. It explains the meaning of deployment statuses (Running, Pending, CrashLoopBackOff, ImagePullBackOff) and provides actionable troubleshooting steps, enriching the agent's understanding of what to expect and how to react.

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 front-loaded with the core purpose in the first sentence, then provides structured, valuable troubleshooting details. It is longer than minimal but each sentence contributes meaningful information, especially the status explanations and remediation steps.

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?

Despite having no output schema, the description thoroughly covers what the tool returns (deployment status, resource usage) and explains how to interpret the statuses. It also anticipates common issues and directs the user to relevant next steps, making it highly complete for a read-only informational tool.

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?

The input schema already describes the single parameter (project_id as UUID) with 100% coverage. The description does not add parameter-specific semantics beyond what the schema provides, so the baseline of 3 is appropriate.

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's function: 'Get detailed project info including deployment status and resource usage.' This provides a specific verb and resource with detailed scope, and the emphasis on deployment status and resource usage distinguishes it from sibling tools like get_project and get_project_usage.

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 provides clear context for when to use the tool (checking deployment status and resource usage) and explicitly recommends an alternative tool (get_schema) for a specific troubleshooting scenario. It does not explicitly state when not to use this tool, but the guidance is strong enough for a 4.

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

All RationalBloks toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation4/5

Most tools are clearly differentiated by domain (project vs graph_project) and action (create, get, list, delete). The main ambiguity is get_project vs get_project_info, which both claim to return detailed project information. Otherwise tool boundaries are clear.

Naming Consistency4/5

The server follows a strong verb_noun convention, with parallel naming for graph and non-graph tools (create_project/create_graph_project, deploy_staging/deploy_graph_staging). Minor deviations include bulk_create_graph_nodes and fulltext_search_graph, but patterns remain predictable.

Tool Count2/5

48 tools is a heavy surface, even when accounting for the two parallel product domains (relational and graph). Many tools are near-duplicates across domains, and the count exceeds the 25-tool threshold that feels manageable. It would benefit from consolidation or sub-servers.

Completeness4/5

Both project types have full life-cycle coverage: create, schema management, deployment, rollback, and deletion, plus graph data operations including bulk, search, and traversal. Minor gaps exist, such as no update_graph_relationship and the redundant get_project/get_project_info pair, but agents can accomplish core workflows.

Resources