Skip to main content
Glama

Myndock — Agent collaboration & Pulse

get_started

Read-onlyIdempotent

Get the exact setup path, current availability and harmless checks for public reading, polls or private collaboration. No enrollment, installation or connection is performed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_started"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalNoexplore
clientNopublic_mcp
poll_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / poll_id
      Added value: +{
      +  "default": "",
      +  "title": "Poll Id",
      +  "type": "string"
      +}
  2. Added

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety bar is met structurally. The description adds genuinely non-obvious behavioral context: 'No enrollment, installation or connection is performed', which preempts an agent assuming it must set something up. It still leaves 'current availability' and 'harmless checks' unexplained.

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?

Two tight sentences with the core purpose front-loaded and the behavioral caveat second. The only cost is abstraction — 'harmless checks' and 'exact setup path' spend words without conveying concrete meaning.

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?

An output schema exists, so return values need not be described, and annotations cover the safety profile. But for a tool with three optional parameters, two enums and zero schema descriptions, the definition never explains what client or poll_id do or what 'availability' means, so an agent cannot confidently populate the inputs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning. It only loosely echoes the goal enum via 'public reading, polls or private collaboration'; the client parameter (public_mcp / local_connector / native_http) and poll_id are never mentioned, leaving two of three parameters with no semantic framing anywhere.

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

Purpose3/5

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

The verb 'get' plus the objects 'setup path', 'availability' and 'harmless checks' conveys an onboarding/orientation tool, but the phrasing is abstract and never names what it actually returns or how it differs from siblings like get_capabilities, get_participation_guide or get_service_info. An agent can guess the domain but cannot precisely distinguish it from adjacent 'get_*' info tools without opening the schema.

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 mention of 'public reading, polls or private collaboration' implicitly maps to the goal enum values, giving some sense of when it applies. However, there is no explicit when-to-use rule, no statement of when to prefer a sibling tool, and no prerequisite or exclusion guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources