get_connected_installationIdentify the linked CasaCaddy Pro installation and its current maintenance-guide allowance. No device identifier, billing data, on-device home library, appliance list or task history is exposed.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
Output schema / anyOfPrevious value: -[
- {
- "additionalProperties": false,
- "properties": {
- "access": {
- "const": "User-supplied appliance details and owner-scoped MCP guide requests only",
- "type": "string"
- },
- "guideAllowance": {
- "additionalProperties": false,
- "properties": {
- "limit": {
- "maximum": 9007199254740991,
- "minimum": 0,
- "type": "integer"
- },
- "used": {
- "maximum": 9007199254740991,
- "minimum": 0,
- "type": "integer"
- }
- },
- "required": [
- "used",
- "limit"
- ],
- "type": "object"
- },
- "label": {
- "type": "string"
- },
- "plan": {
- "const": "pro",
- "type": "string"
- },
- "synthetic": {
- "type": "boolean"
- }
- },
- "required": [
- "label",
- "synthetic",
- "plan",
- "guideAllowance",
- "access"
- ],
- "type": "object"
- },
- {
- "additionalProperties": false,
- "properties": {
- "error": {
- "minLength": 1,
- "type": "string"
- },
- "message": {
- "type": "string"
- },
- "quota": {
- "additionalProperties": false,
- "properties": {
- "limit": {
- "maximum": 9007199254740991,
- "minimum": 0,
- "type": "integer"
- },
- "used": {
- "maximum": 9007199254740991,
- "minimum": 0,
- "type": "integer"
- }
- },
- "required": [
- "used",
- "limit"
- ],
- "type": "object"
- }
- },
- "required": [
- "error"
- ],
- "type": "object"
- }
-]New value: +[
+ {
+ "additionalProperties": false,
+ "properties": {
+ "access": {
+ "const": "User-supplied appliance details and owner-scoped MCP guide requests only",
+ "type": "string"
+ },
+ "guideAllowance": {
+ "additionalProperties": false,
+ "properties": {
+ "limit": {
+ "maximum": 9007199254740991,
+ "minimum": 0,
+ "type": "integer"
+ },
+ "used": {
+ "maximum": 9007199254740991,
+ "minimum": 0,
+ "type": "integer"
+ }
+ },
+ "required": [
+ "used",
+ "limit"
+ ],
+ "type": "object"
+ },
+ "label": {
+ "type": "string"
+ },
+ "plan": {
+ "const": "pro",
+ "type": "string"
+ },
+ "reviewerAccess": {
+ "additionalProperties": false,
+ "properties": {
+ "freshRequestsRemaining": {
+ "maximum": 20,
+ "minimum": 0,
+ "type": "integer"
+ },
+ "maxFreshRequestsTotal": {
+ "const": 20,
+ "type": "number"
+ },
+ "mode": {
+ "enum": [
+ "stored_examples",
+ "bounded_live"
+ ],
+ "type": "string"
+ }
+ },
+ "required": [
+ "mode",
+ "freshRequestsRemaining",
+ "maxFreshRequestsTotal"
+ ],
+ "type": "object"
+ },
+ "synthetic": {
+ "type": "boolean"
+ }
+ },
+ "required": [
+ "label",
+ "synthetic",
+ "plan",
+ "guideAllowance",
+ "access"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": false,
+ "properties": {
+ "error": {
+ "minLength": 1,
+ "type": "string"
+ },
+ "message": {
+ "type": "string"
+ },
+ "quota": {
+ "additionalProperties": false,
+ "properties": {
+ "limit": {
+ "maximum": 9007199254740991,
+ "minimum": 0,
+ "type": "integer"
+ },
+ "used": {
+ "maximum": 9007199254740991,
+ "minimum": 0,
+ "type": "integer"
+ }
+ },
+ "required": [
+ "used",
+ "limit"
+ ],
+ "type": "object"
+ }
+ },
+ "required": [
+ "error"
+ ],
+ "type": "object"
+ }
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds non-obvious scope disclosure by enumerating what is NOT exposed (device identifier, billing data, on-device library, appliance list, task history), which meaningfully bounds expectations beyond the structured fields.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two tight sentences with zero waste. The core purpose is front-loaded and the exclusion list that follows earns its place by setting privacy/scope expectations.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values need no explanation, and there are no parameters to document. Combined with read-only annotations and explicit exclusion scoping, the definition is sufficient to call correctly, though it stops short of stating when this lookup should be performed relative to its siblings.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so the baseline is 4; there is nothing parameter-wise the description needs to compensate for. It correctly adds no redundant parameter prose.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('Identify') and resource (the linked CasaCaddy Pro installation) plus the salient return attribute (maintenance-guide allowance). This clearly distinguishes it from the guide-retrieval siblings, but the description never names or contrasts those siblings explicitly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no explicit when-to-use, when-not-to-use, or alternative-tool guidance. The 'linked installation' framing implies this is the entry-point lookup for installation context, which is adequate implied usage but leaves the agent to infer when get_maintenance_guide or get_saved_guide_request is the better call.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.