Skip to main content
Glama
Sign In
io.github.Evin009/smartrent-mcp

io.github.Evin009/smartrent-mcp

by Evin009
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

lock_door

Lock or unlock the front door remotely by specifying 'lock' or 'unlock' as the action.

Instructions

Lock or unlock the front door. action: 'lock' or 'unlock'

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": {
      "action": "<action>"
    },
    "name": "lock_door"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are present, so the description must carry the full burden. It only states the action parameter values but does not disclose side effects, failure modes, or state behavior (e.g., what happens if already locked). Minimal behavioral info.

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?

Two sentences with no redundant info. The main purpose is front-loaded, and the action values are clearly specified. Every word earns its place.

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 tool is simple with one parameter, and the description covers its core purpose and allowed values. However, it omits return value behavior (though an output schema exists), error conditions, and any prerequisites. Adequate but not thorough.

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?

Schema coverage is 0% with a simple string parameter. Description explicitly lists allowed values 'lock' and 'unlock', adding clarity beyond the raw schema. This compensates for the lack of enum constraints.

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?

Description clearly states 'Lock or unlock the front door', which is a specific verb+resource pair. It distinguishes from siblings like ping, get_device_status, switch_control, and set_temperature, which are for different devices.

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?

No guidance on when to use lock vs unlock, or when to prefer this tool over alternatives. No prerequisites or context provided.

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