Skip to main content
Glama

ArchGuard MCP

recommend_architecture

Generate a Staff-level distributed system architecture blueprint from workload traits (consistency, R/W ratio, contention, real-time need, latency SLO).

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

Input Schema

NameRequiredDescriptionDefault
dataModelNo
scaleTierNo
consistencyNo
latencySloMsNo
realtimeNeedNo
contentionLevelNo
readWriteProfileNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations present, the description carries the full behavioral burden, yet it discloses nothing about side effects, determinism/idempotency, or whether generated blueprints are persisted or purely advisory. It also gives no sense of the output's shape or depth, which matters for a generative recommendation tool with no output schema.

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?

One front-loaded sentence with no filler and the output artifact stated first. It is efficient, though the terseness leaves little room for the guidance the complex input space requires.

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

Completeness2/5

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

A seven-parameter generative tool with zero annotations, no output schema, and zero parameter descriptions demands far more than a single sentence. Notably, all parameters are optional, so the description should explain defaults or what happens when traits are omitted, and it says nothing about that.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate, but it only echoes five of the seven inputs (consistency, R/W ratio, contention, real-time need, latency SLO) without defining units, valid ranges, or how each trait changes the recommendation. dataModel and scaleTier are not mentioned at all, and the loose phrasing ('R/W ratio') diverges from the actual 'readWriteProfile' enum.

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 names a specific verb and artifact ('Generate a Staff-level distributed system architecture blueprint') and enumerates the workload traits that drive it, which is enough for an agent to tell it apart from the simulate_*/estimate_system_capacity siblings. It stops short of explicitly contrasting with any sibling, so a 4 rather than a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use statement, and no routing to alternatives such as estimate_system_capacity or simulate_quorum_and_tail_latency. The list of traits only hints that the tool is invoked when those traits are known; the agent must infer the rest.

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.