Skip to main content
Glama

studio_ninja_guide

Learn how to work in Studio Ninja—leads, jobs, contracts, invoices, overdue payments, screens, and sign-in—and call this first to plan actions.

Instructions

How to work in Studio Ninja (leads, jobs, contracts, invoices and overdue payments): 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": "studio_ninja_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in Studio Ninja, 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 carries the full disclosure burden, and it does signal that the tool returns reference content about screens plus a sign-in link — implying a read-only informational lookup. It does not state the response format, whether the guide is static or tailored to the task argument, or any limits, which leaves real gaps for a tool with zero annotation coverage.

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 tight sentences with no filler, and the scope is front-loaded. Moving the imperative "Call this first" to the opening would slightly improve routing, but nothing is wasted.

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?

The tool is simple (one optional free-text param, no output schema, no nested objects), and the description says what subject matter is covered. Still missing is what an agent actually receives back and how the optional task argument changes it, which matters because that argument is the only input the tool takes.

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 description coverage is 100% and there is a single optional parameter whose schema text ("What you want done in Studio Ninja, in your words") already explains it. The description adds no meaning about how the free-text task shapes the guide returned, which is the one ambiguity the schema cannot resolve; baseline 3 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 resource — an orientation guide to Studio Ninja — and scopes it with concrete domains (leads, jobs, contracts, invoices, overdue payments), screens, and the sign-in link. It is clearly distinguishable from the sibling UI-action tools (click, open, read, type), though it never explicitly contrasts itself with them.

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, actionable ordering instruction that tells the agent when to reach for this tool relative to everything else. It stops short of a full when/when-not rule (e.g. whether to skip it if you already know the screens), so it is clear context rather than exhaustive guidance.

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