Skip to main content
Glama

oto_photo_status

Check that your Cotlet.dev account, credits, and oto.photo connection are ready before starting photo workflows.

Instructions

Check that your Cotlet.dev account and oto.photo are ready: account, credits and oto.photo 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": "oto_photo_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does communicate that this is a non-mutating readiness check covering three specific facets, which is the core behavioral fact, but it says nothing about what the result looks like, whether credits are consumed, or whether it requires authentication.

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?

One short sentence, front-loaded with the verb and the three checked facets. Slight redundancy in restating 'account ... and ... connection' as a colon-separated list, but no wasted sentences.

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 zero-parameter status tool this is close to adequate, but with no output schema and no annotations, the agent has no idea what the response contains (booleans per facet? a message? an error when not ready?). One clause about the return shape would close the gap.

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 no parameter meaning to convey; the baseline for a parameterless tool applies. The description correctly implies no input is needed.

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 verb ('Check') and enumerates exactly what is verified: account status, credits, and the oto.photo connection. That is enough to distinguish it from the sibling tools (click/close/open/read/type), which are page-interaction actions, though it never explicitly says so.

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?

The phrase 'ready' implies a pre-flight/diagnostic use case, which is a reasonable hint about when to call it. However, there is no explicit statement of when to prefer this over, say, oto_photo_open, nor any mention of prerequisites or repeated-call behavior.

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