Skip to main content
Glama

monograph_status

Verify your Cotlet.dev account, available credits, and Monograph connection are ready before running project, staffing, or billing tasks.

Instructions

Check that your Cotlet.dev account and Monograph are ready: account, credits and Monograph connection.

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_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

No annotations exist, so the description carries the full disclosure burden. It helpfully enumerates the three things verified (account, credits, connection), but says nothing about whether the call is read-only, whether it consumes credits, whether it can trigger an auth/connect flow, or what happens when a check fails.

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 front-loaded sentence with a colon-delimited enumeration of what is checked; no filler, no restatement of the tool name, and the scope is clear at a glance.

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 trivial zero-param tool this is close to sufficient, but with no output schema the description should describe what a result looks like (e.g., per-item ready/not-ready status versus a thrown error), which it does not.

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 and the schema is a closed empty object, so there is no parameter meaning for the description to add; baseline for a parameterless tool applies.

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 ('Check') and a specific set of resources ('account, credits and Monograph connection'), so an agent knows this is a readiness/preflight diagnostic rather than a Monograph action. It is implicitly distinguishable from the sibling UI-action tools (open/click/type/read), but the description never contrasts itself with them 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: the framing 'check that ... are ready' suggests running it before attempting Monograph operations, but there is no explicit when-to-use or when-not-to-use statement and no mention of prerequisites or alternatives.

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