Skip to main content
Glama

get_help

Read-onlyIdempotent

Displays documentation for LinkedIn MCP tools and their input schemas, helping you identify the right tool and understand required parameters.

Instructions

Show tool documentation.

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

Input Schema

NameRequiredDescriptionDefault
toolNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered; the description adds nothing beyond them. It does not mention scope of returned docs, whether the list of tools is included, or any limits, so an agent learns nothing new about behavior from the prose.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with no filler, so nothing is wasted. But the brevity comes at the cost of under-specification rather than being tightly front-loaded information.

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?

An output schema exists, so return values need not be described, but for a help/discovery tool the description should at minimum explain what the argument does and what happens with no argument. Given the 0% parameter coverage, the definition is too thin for an agent to invoke it confidently.

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% and the single parameter "tool" is undocumented in both schema and description. The description never explains that the parameter takes a tool name, nor what the empty-string default produces, so it fails to compensate for the coverage gap.

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?

"Show tool documentation" gives a verb (show) and a resource (tool documentation), so the agent knows this is a meta/documentation lookup rather than a job-search action. However, it does not say whose documentation (the server's own tools?) or what the documentation contains, so it is only loosely distinguishable from siblings like get_usage_stats or get_engine_status.

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 instead of any other tool, and no mention that it is a discovery/help mechanism. The key behavioral question - whether omitting the argument lists all tools versus returning general help - is left entirely unstated.

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