Skip to main content
Glama
Sign In

Radar noEixo

by com.noeixodigital
OverviewDiscussionsAdmin

Connect neetocal

connect_neetocal

Conecta a conta a um scheduling link do NeetoCal, o provedor de agenda alternativo ao Google Calendar. Fluxo em 2 passos: 1) chame SEM meeting_slug — valida a chave e retorna a lista de scheduling links disponíveis no workspace (com hosts e duração); 2) escolha um slug da lista e chame de novo COM meeting_slug para salvar a conexão de fato. Cada meeting_slug vira UMA conexão própria — chame de novo com um slug DIFERENTE para adicionar outro profissional/link (ex: um round-robin geral + um link individual de cada closer), sem apagar os anteriores. Depois de conectar, ative calendar_booking_mode via update_agent_config para o agente passar a usar as tools de agendamento (check_availability, schedule_appointment, etc.).

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": {
      "api_key": "<api_key>",
      "subdomain": "<subdomain>"
    },
    "name": "connect_neetocal"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelNoNome de exibição do profissional/link (opcional; padrão = nome do meeting no NeetoCal). Ex: "Pablo Costa".
api_keyYesChave de API do NeetoCal (Painel de administração > Chaves da API), começa com "NCAL-".
subdomainYesSubdomínio do workspace NeetoCal, ex: "ekyte" (de https://ekyte.neetocal.com).
is_defaultNoSe "true", marca esta conexão como a PADRÃO — usada automaticamente pelo agente sem perguntar ao cliente quem prefere. As demais conexões (Google Calendar ou NeetoCal) da conta são desmarcadas como padrão. Se a conta tem só uma conexão, ela já funciona sozinha independente disso. Com 2+ conexões, marque uma como padrão (geralmente o link de round-robin) para as outras virarem "alternativas nominais" — só usadas se o cliente pedir uma pessoa específica por nome.
meeting_slugNoSlug do scheduling link a usar (opcional na 1ª chamada — descubra os disponíveis via a resposta sem esse campo). Cada slug distinto vira uma conexão própria.
target_user_idNoID da conta-alvo (opcional; APENAS o admin da plataforma pode usar). Padrão: a conta autenticada.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true), it discloses the non-obvious behavior that each distinct meeting_slug creates a SEPARATE connection and prior ones are not deleted, that is_default unsets other connections as default, and that target_user_id is admin-only. It also pre-announces what the first (slugless) call returns — the scheduling link list with hosts and duration — which is not discoverable from the schema since there is no output schema.

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?

Front-loaded with purpose, then the numbered flow, then consequences and next step — a sensible ordering. It is somewhat long and the parenthetical example about round-robin plus individual closer links could be trimmed, but nearly every sentence carries operational information.

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

Completeness5/5

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

For a 6-parameter, no-output-schema mutation tool, the description covers the full lifecycle: prerequisite inputs, the two-phase call sequence, the content returned by phase one, additivity of repeated calls, default-marking semantics, and the config change required to activate booking tools. Nothing an agent needs to invoke it correctly is missing.

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 100%, so the baseline would be 3. The description nonetheless adds real meaning: it explains the discovery-then-select pattern for meeting_slug and the side effects of is_default (other connections are unset as default), which the schema only states briefly. api_key, subdomain and label get no extra treatment because the schema already covers them well.

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?

States a specific verb and resource ('Conecta a conta a um scheduling link do NeetoCal') and positions it against the obvious alternative provider ('o provedor de agenda alternativo ao Google Calendar'). An agent immediately knows this is a connection/credential setup action, not a booking or listing action like list_bookings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit two-step protocol: first call WITHOUT meeting_slug to validate the key and enumerate links, then call again WITH a chosen slug to persist the connection. It also names the follow-up prerequisite ('ative calendar_booking_mode via update_agent_config') and the sibling tools that only work afterwards (check_availability, schedule_appointment), so the agent knows exactly what to do before and after.

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

All Radar noEixo toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources