get_project
Get one public project case study summary by slug.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| projectslug | Yes |
Raze
TDQS
A3.5/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations. Description only states basic action without disclosing what happens on missing slug, required permissions, or return behavior.
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?
Single sentence, front-loaded with action and resource. No wasted words.
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?
Adequate for a simple get-by-identifier tool with 1 param. Lacks details on return format and error handling, but enough for basic use.
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?
Description adds 'by slug' to parameter context beyond enum schema. Schema coverage 0% but description partly compensates by clarifying parameter purpose.
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?
Description clearly states the verb 'Get' and resource 'one public project case study summary' by slug. Distinguishes from sibling 'list_projects' which lists multiple.
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?
Implied usage: use when you need a single project by slug. No explicit when-not-to or alternatives, but context is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.8/5.0
Disambiguation5/5
Each tool targets a distinct aspect of Raze's public information or booking functionality. There is no overlap; booking, pricing, projects, resources, and services are clearly separated.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_booking, get_available_slots, list_projects). This makes it easy for an agent to predict tool behavior.
Tool Count5/5
With 10 tools, the server covers the main public-facing aspects of Raze (booking, pricing, projects, resources, services) without being overly heavy or thin. Each tool serves a clear purpose.
Completeness5/5
The tool set provides comprehensive coverage for a company site: booking lifecycle (including slot checking and creation), pricing, project case studies (list and detail), resources, and services. No obvious gaps for the intended public interaction.