Skip to main content
Glama
Sign In
careops-mcp

careops-mcp

by ZGhey
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

schedule_visit

Schedule a care visit for a client with a carer, ensuring valid date, time, and duration, and preventing double-booking.

Instructions

Schedule a care visit. Input is strictly validated (Pydantic).

Rejects past dates, malformed times, and out-of-range durations before anything touches the database. Refuses to double-book a carer at an already-scheduled date and start time.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "request": "<request>"
    },
    "name": "schedule_visit"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of disclosing behavior. It thoroughly explains validation checks (past dates, malformed times, out-of-range durations, double-booking refusal), giving a clear picture of what the tool will and won't do. However, it does not discuss authentication, side effects on database, or success response.

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?

The description is concise, with three short sentences that front-load the main purpose and then add essential behavioral details. No unnecessary words.

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 description covers validation and double-booking but omits prerequisites (e.g., client/carer existence), success output (likely covered by output schema), and any side effects. Adequate but with notable gaps.

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?

The input schema has detailed descriptions for each property, so schema coverage is effectively high (despite context signal claiming 0%). The tool description adds no parameter-level meaning beyond validation context, so it meets the baseline of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose as 'Schedule a care visit.' It uses a specific verb-resource pair and distinguishes it from siblings like check_compliance, get_client, etc., which are unrelated to scheduling.

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 description implies when to use the tool (to schedule a visit) but does not provide explicit when-not-to-use instructions or alternative tools. It mentions validation and double-booking rejection, which helps but falls short of full guidance.

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

Deploy Server

Other Tools