Skip to main content
Glama
Sign In

Sharelint

by com.sharelint
OverviewDiscussionsAdmin

Full link audit

check_url
Read-onlyIdempotent

Run every Sharelint check on a URL at once: link previews in 12 apps, AI visibility for ChatGPT, Claude and Perplexity, iOS and Android app links, and performance. Use it for a general "check my website or link" request; use the focused tools when the question is about one of these.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "check_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL or bare domain to check, for example "example.com/pricing". Private and local addresses are refused.
crawlerNoUser-Agent to fetch the page as for share previews. Defaults to Facebook’s crawler, which most apps resemble.facebook

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare read-only, open-world, idempotent, non-destructive behavior, so the description adds useful context by explaining what the audit actually performs: link previews, AI visibility, app links, and performance, all at once. It stops short of explaining the return shape, runtime implications, or combined-report behavior, so it is not fully transparent.

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?

The description is two sentences, front-loaded with the operation and scope, followed by the usage rule. Every sentence earns its place with no repetition or filler.

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 two-parameter aggregate audit with rich annotations and full schema coverage, the description covers purpose, scope, and alternative selection well. It does not spell out the combined report's return shape, which is the main remaining gap given there is no output schema.

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?

Schema description coverage is 100%; both the url and crawler parameters are fully documented in the schema, including the default crawler and the refusal of private/local addresses. The description adds no parameter-level meaning beyond saying it runs checks on a URL, so the baseline score of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description starts with a specific verb and resource: 'Run every Sharelint check on a URL at once.' It enumerates the five check areas and explicitly contrasts this aggregate audit with focused tools, so an agent can distinguish it from siblings without opening the schema.

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

Usage Guidelines5/5

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

It gives a clear selection rule: use this for a general 'check my website or link' request, and use the focused tools when the question is about one specific area. The alternatives are referenced by category, which is sufficient even though exact sibling tool names are not repeated.

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

All Sharelint toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources