Skip to main content
Glama

Linken status

linken_status
Read-only

Checks LinkedIn API connectivity via one read-only userinfo request and reports token validity, member name, author URN, API version, dry-run mode, and recent ledger entries.

Instructions

Checks the LinkedIn connection with one read call (GET /v2/userinfo), sent through the trusted helper. Returns the member's name, the author URN (urn:li:person:{sub}), whether the token works, the pinned LinkedIn API version, whether dry-run is on, and the last 5 ledger lines. With LINKEN_DRY_RUN=1 it sends nothing and returns the request it would send. It publishes nothing and returns no token.

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": "linken_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

A3.9/5.0
Behavior4/5

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

readOnlyHint=true is already declared, yet the description still earns credit by disclosing side-effect scope: 'It publishes nothing and returns no token,' and that dry-run mode sends nothing and echoes the would-be request. That goes well beyond the annotation. It does not mention auth prerequisites or error behaviour, keeping it out of the top band.

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?

Three tight sentences, front-loaded with the action and endpoint before the return payload. Every sentence carries information; the enumerated return fields are dense but purposeful. Slightly list-like rather than fully structured.

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?

No output schema exists, so the description must carry the return contract — and it does, naming the member name, author URN format, token validity, pinned API version, dry-run flag, and ledger lines. For a zero-parameter diagnostic tool this is complete.

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?

The tool takes zero parameters, so the baseline of 4 applies. Nothing in the description is needed to clarify inputs.

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 concrete verb+resource: 'Checks the LinkedIn connection with one read call (GET /v2/userinfo)', and names the mechanism (trusted helper). An agent knows exactly what this does. It does not explicitly contrast with sibling connections_check, so it stops 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 Guidelines3/5

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

Usage is only implied — this is a diagnostic/status probe, and the LINKEN_DRY_RUN=1 detail hints at a preflight use case. There is no explicit 'use this when…' or 'use X instead for…' guidance, and no mention of when it should not be called.

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