Skip to main content
Glama

Check endpoint URL

check_endpoint
Read-onlyIdempotent

What lcas has stored about one MCP, A2A or web endpoint URL, for a client about to connect to it: last check and 30-day history, when its tool list last changed, a tools_pin (save it when you approve the tools; a different pin later means lcas read a changed list), tools whose text matched the tool-poisoning scan, the live and guard tests, and the listed agents that declare the URL. No matches means no listed agent declares this URL, which says nothing about it. Built from stored checks; nothing is called.

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

Input Schema

NameRequiredDescriptionDefault
urlYesThe endpoint URL, as you would connect to it (https://...).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld=false/idempotent/non-destructive, and the description still adds real value beyond them: 'Built from stored checks; nothing is called' confirms no live fetch happens, and the caveat that no matches 'says nothing about it' tells the agent how to interpret an empty result. The tools_pin semantics (a different pin means a changed list; the pin is tied to the endpoint URL, not tool contents) are behavioral context the annotations cannot convey.

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?

The content is dense and useful, but the first sentence is an overlong run-on with many comma-separated clauses of return-field inventory. Key scoping facts (nothing is called, no-match means nothing) are buried mid-paragraph rather than front-loaded, costing readability.

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?

There is no output schema, so the description carries the full burden of explaining the return payload, and it does so thoroughly: 30-day history, change timestamps, tools_pin, poisoning-scan matches, live and guard tests, and declared agents. For a read-only, single-parameter lookup, an agent has enough to call it and interpret results correctly.

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 coverage is 100% and the single url parameter is documented in the schema with format guidance, so the baseline is 3. The description reinforces that it must be an endpoint URL you would actually connect to, but adds no format, normalization, or encoding detail beyond the schema.

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 opens with a concrete statement of the resource: stored information about one MCP, A2A or web endpoint URL, including check history, tool-list changes, a tools_pin, and match results. The purpose is unmistakable and clearly narrower than a directory or search tool, though it never names the close sibling (check_agent) to delimit scope between the two.

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?

It gives explicit when-to-use context ('a client about to connect to it') and an explicit when-not with an alternative ('not for checking OpenAPI specs/docs pages; call check_web_url when the URL is not an MCP endpoint'). The only gap is that it does not route between this and check_agent, which is the most adjacent sibling.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources