Skip to main content
Glama

evite_status

Check that your Cotlet.dev account, credits, and Evite connection are ready before using Evite tools.

Instructions

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and does not discharge it. It does not say whether the call performs live network checks, whether it costs or consumes credits, what the response looks like, or what an agent should do when a component reports not ready.

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 front-loaded sentence with a colon-delimited list of what is checked; there is no filler. The phrasing 'Check that your ... are ready' is slightly conditional in tone but wastes no space.

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 diagnostic this covers what is checked, but with no annotations and no output schema, the description leaves the return shape and failure handling entirely unspecified. An agent knows what to call but not what it will get back or how to react.

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 are no parameter semantics to explain and the baseline of 4 applies. The description correctly implies no input is required to run the check.

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 gives a specific verb ('Check') and enumerates the exact resources verified: account, credits, and Evite connection. This is distinguishable from the sibling action tools (evite_open, evite_click, evite_read, etc.), though it never explicitly names itself as a pre-flight readiness check.

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: an agent can infer this should be run before attempting Evite actions, since readiness preconditions are its purpose. There is no explicit statement of when to call it, when not to, or which sibling to use instead if a check fails.

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