Skip to main content
Glama

app_status

Read-only

Checks whether FilmCraft is currently driving the app and reports which project is open, so you can confirm the connection and active project before editing.

Instructions

Whether this server is driving the FilmCraft app, and which project the app has open.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the return content (app-driving flag plus open project), which is useful since there is no output schema, but it does not say what is reported when the app is not connected or no project is open.

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 economical sentence with no filler, and the core subject (server driving the app) comes first. The noun-clause phrasing ('Whether...') is slightly indirect but does not cost comprehension.

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-parameter status tool with no output schema, the description covers the gist of the return values but leaves the exact shape and the disconnected/no-project cases unspecified. Adequate, but not complete enough to tell an agent precisely what to expect back.

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 there is nothing for the description to disambiguate and the baseline of 4 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?

The description names a specific resource (this server's status relative to the FilmCraft app) and the two facts it reports: whether the app is being driven and which project is open. It is distinguishable from siblings like connect_app or inspect_project, though the verb is implicit rather than a clear 'report/check'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no guidance on when to call this versus connect_app/disconnect_app, nor any stated precondition (e.g., call before project operations to confirm the app has a project open). The agent must infer the use case from the description alone.

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