Skip to main content
Glama

monograph_guide

Guides you through Monograph's screens, sign-in link, and workflows for projects, staffing, budgets, time, and billing so firm management tasks are completed in the right order.

Instructions

How to work in Monograph (architecture and engineering firm management with projects, staffing, budgets, time and billing): its screens and the sign-in link. Call this first.

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

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in Monograph, in your words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden itself. It discloses the content surface (screens and the sign-in link), implying this is a passive informational lookup, but it never states that the tool is read-only, whether the response is prose documentation or links, or whether the returned guidance is scoped by the task argument.

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?

Two compact sentences with the domain gloss parenthetically placed and the routing directive at the end. Nothing is wasted, though the parenthetical field list is arguably filler for an agent.

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?

For a one-optional-parameter, no-output-schema tool this is nearly sufficient, but it leaves the agent guessing whether the result is documentation text, a URL, or a step list, and whether the returned content varies with the task argument.

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?

Schema coverage is 100% and the single 'task' parameter is fully described in the schema as 'What you want done in Monograph, in your words.' The description adds nothing about how the task string shapes the returned guidance, so it sits at the high-coverage baseline.

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 resource (Monograph, an architecture/engineering firm management system) and scopes its content to 'its screens and the sign-in link,' which tells an agent this is an orientation/documentation tool rather than an action tool. It does not explicitly contrast itself with siblings like monograph_click or monograph_read, keeping it from 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 Guidelines4/5

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

'Call this first' is an explicit, unambiguous usage directive that establishes ordering relative to every other Monograph tool. It stops short of stating when NOT to use it or naming an alternative path once orientation is complete.

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