Skip to main content
Glama
Sign In
@instantreply/mcp

@instantreply/mcp

by suleimandoescsec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_developer_onboarding

Read-only

Retrieve the developer onboarding checklist for your current workspace to set up the @instantreply/mcp inbox integration correctly and completely.

Instructions

Get the developer onboarding checklist for the current workspace.

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_developer_onboarding"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this is a safe read-only, non-destructive operation, so the safety profile is fully covered. The description adds the scoping constraint ('current workspace') but nothing about auth needs, checklist composition, or freshness. With annotations carrying the safety burden, this is adequate but thin.

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?

One sentence, front-loaded with the verb, and it earns its place by naming the resource and scope. No filler.

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?

For a zero-param, annotation-covered read tool, the essentials are present. However, it lacks any hint of what the checklist contains or when an agent should reach for it, which matters given the dense sibling cluster of developer-oriented tools.

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?

Zero parameters, so baseline is 4. The description correctly frames the implicit workspace context rather than pretending there are inputs. Nothing further is needed.

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?

States a specific verb (Get) and resource (developer onboarding checklist) scoped to the current workspace. It's clear what the tool returns, but it doesn't distinguish itself from siblings like get_developer_limits or get_developer_capabilities — the reader must infer the difference from the resource noun alone.

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 indication of when to use this versus siblings like get_developer_capabilities or get_connection_guide. The 'current workspace' scoping implies a context but provides no conditions, prerequisites, or alternatives.

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