Skip to main content
Glama
architectural_modeling_workflow

architectural_modeling_workflow

by Lsc1123

project_get

Read-onlyIdempotent

Retrieve current project facts, decisions, checks, pending issues, and revision to track state and keep architectural modeling work aligned.

Instructions

Read current facts, decisions, checks, pending issues and revision.

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

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.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds scoping by listing what the snapshot contains and that it reflects 'current' state plus a revision marker, but says nothing about pagination, size limits, or behavior when no project exists.

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?

A single short sentence with the verb first and the payload enumerated; every word carries information and there is no filler or repetition.

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 zero-parameter read tool with an output schema and full annotation coverage, the description supplies enough to call it correctly and to know what the response represents. The only meaningful gap is the absence of any statement about prerequisites, such as whether a project must first be created via project_init.

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; the description correctly implies no arguments are needed because the call is scoped to the current project context. Nothing about parameter meaning is left ambiguous.

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?

States a specific verb (Read) and enumerates the resource contents returned: facts, decisions, checks, pending issues, revision. This clearly distinguishes it from mutation siblings like project_update or project_init, though it never names those siblings explicitly.

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: a zero-parameter 'Read' of current project state is self-evidently the retrieval entry point, and the word 'current' hints at calling it before acting. There is no explicit when-to-use, when-not-to-use, or reference to alternatives such as the individual decision_record or checks_run tools.

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