Skip to main content
Glama
architectural_modeling_workflow

architectural_modeling_workflow

by Lsc1123

get_capabilities

Read-onlyIdempotent

Inspect the live software connection, model units, workflow stages, and validation limits to verify your architectural modeling setup before proceeding.

Instructions

Inspect actual software connection, units, stages and validation limits.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds meaningful context beyond that by indicating it probes live/actual state (connection, units, validation limits) rather than returning cached or static metadata.

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?

A single front-loaded sentence fragment with no filler. It is terse to the point of being slightly clipped (no subject or object noun like "environment"), but nothing is wasted.

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 no-parameter, read-only inspection tool with an output schema and full annotations, the description covers what the call reports and needs no return-value explanation. Only a note on when in a workflow to call it is missing.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4 and there is nothing for the description to clarify. The schema is empty by design and the description correctly does not invent inputs.

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 pairs a concrete verb ("Inspect") with a specific set of reported facts: software connection, units, stages, and validation limits. That is enough to tell it apart from the SketchUp mutation/query siblings, though "stages" and "software connection" are vague as to what exactly is being inspected.

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?

Usage is only implied: the word "actual" hints this should be called to verify real environment state rather than assumed config. There is no explicit statement of when to call it, when not to, or which siblings it complements (e.g., before running asset or checker operations).

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