evo-mcp

authorize_entry

Authorize or deny gym user access through EVO access control by validating user ID, person type, device, and turnstile credentials.

Instructions

Autoriza ou nega acesso de um usuário à academia

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": {
      "userId": "<userId>",
      "personType": "<personType>",
      "device": "<device>",
      "turnstileId": "<turnstileId>"
    },
    "name": "authorize_entry"
  }
}

Input Schema

Name	Required	Description
`device`	Yes	Tipo de dispositivo: 1=Digital, 2=QR Code, 3=Facial, 4=Teclado
`userId`	Yes	ID do usuário
`climateId`	No	ID do clima (opcional): 1=Ensolarado, 2=Frio, 3=Chuva, 4=Tempestades, 5=Neve, 6=Nublado, 7=Ventoso
`personType`	Yes	Tipo de pessoa: 1=Cliente, 2=Oportunidade, 3=Colaborador, 4=Personal
`temperature`	No	Temperatura (opcional)
`turnstileId`	Yes	ID da catraca

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 13, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations exist, so the description carries the full burden. It does not disclose whether the call physically opens a turnstile, logs an access event, requires prior authentication, or what the decision response looks like — all critical for an access-control mutation. 'Autoriza ou nega' implies a decision but not its side effects.

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 no filler or redundancy. It is efficient, though almost too terse for the complexity of the operation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 6 parameters (4 required), no annotations, and no output schema, the description should explain the decision outcome and side effects. Instead it gives one sentence, leaving the agent without enough to call the tool confidently or interpret its result.

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?

Schema description coverage is 100%, with clear enum labels (device, personType, climateId) and descriptions, so the schema does the heavy lifting. The description adds no parameter meaning beyond that, which is the expected baseline when coverage is complete.

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 states a specific action and outcome: authorizing or denying a user's access to the gym. However, it does not differentiate this tool from the sibling authenticate_member, which an agent could easily confuse with it, so it falls short of a 5.

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?

There is no guidance on when to call this tool versus authenticate_member or get_member_profile, no prerequisites, and no statement of what the caller is expected to supply as a pre-check. The agent must infer usage entirely.

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

Deploy Server