Skip to main content
Glama
omnipost-social-engine

omnipost-social-engine

by 1nc0gn30

omni_get_diagnostics

Retrieve system diagnostics, platform character limits, Unicode font support status, and engine version details to validate posting constraints and troubleshoot engine behavior.

Instructions

Retrieve system diagnostics, platform character limits, Unicode font support status, and engine version info.

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

Input Schema

NameRequiredDescriptionDefault
platformNoOptional specific platform query.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.5.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden. 'Retrieve' signals a read-only, low-risk operation, and the enumerated content areas hint at the return surface, but permissions, caching, cost/latency, and whether results are static or live are all undisclosed. Adequate for a simple read, 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.

Conciseness4/5

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

One front-loaded sentence with no filler; each listed item is a distinct content category. Slightly list-like, but nothing is redundant.

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?

For a zero-required-parameter read tool with no output schema, enumerating the returned content categories is the right compensation and it does so. The gap is that 'system diagnostics' remains an unelaborated catch-all, so an agent cannot fully predict the payload.

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

Parameters3/5

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

The single optional 'platform' parameter is fully documented in the schema (100% coverage), so the baseline is 3. The description says 'platform character limits' which loosely relates to it but adds no meaning about what values are accepted or what happens when the parameter is omitted (presumably all platforms).

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 ('Retrieve') plus the resource categories returned: system diagnostics, platform character limits, Unicode font support, and engine version. That is enough for an agent to distinguish it from formatting/URL/campaign siblings. It stops short of explicitly naming what it is not, so no sibling differentiation is asserted.

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: an agent can infer it should call this when it needs platform limits or version info before formatting content. There is no explicit 'use when' statement, no prerequisites, and no mention of when not to call it.

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