Skip to main content
Glama

instagram_health

Read-onlyIdempotent

Reports local dependencies and verified capabilities for Instagram Obscura MCP, so you can confirm the environment is ready without checking Instagram login.

Instructions

Report local dependencies and verified capabilities; this does not check Instagram login.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds meaningful context beyond that: it is a local-only probe that does not touch Instagram auth, which tells the agent it is safe and cheap to call in any state. It does not mention cost/latency or what a failing result implies.

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 short sentence, front-loaded with the action and scope, followed by the single disambiguation clause that matters. Nothing is redundant or padded.

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

Completeness4/5

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

With no parameters, rich annotations and an output schema, the description supplies exactly what structured fields cannot: that this is a local diagnostic and not an auth check. Slightly more on what a positive vs negative result means to the caller would make it 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 there is no parameter meaning to convey and the baseline of 4 applies. The description correctly spends no words on arguments.

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?

The description names a specific action (report) and a specific resource (local dependencies and verified capabilities), which is enough for an agent to distinguish this diagnostic tool from the instagram_* action tools. The only softness is 'verified capabilities', which is a bit abstract without saying what capabilities look like.

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

Usage Guidelines4/5

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

The clause 'this does not check Instagram login' explicitly rules out the most likely mis-invocation and implicitly routes the agent to instagram_login_status for auth state. It lacks a positive 'use this before attempting actions to confirm local dependencies' statement, so the when-to-use side is inferred rather than stated.

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