Skip to main content
Glama

AgentMart

by ai.ciphyr.agentmart
OverviewDiscussionsAdmin

Run a free site check

check_site
Read-only

Free. Reads a website's public facts: HTTPS and headers, certificate dates, SPF and DMARC, privacy, terms and contact pages, llms.txt, robots.txt and MCP labels. At most 24 requests, one over plain http, and up to 5 of them to its MCP server if it names one. Never logs in or posts forms. Each check: pass, warn, fail or not checked, with fixes. The same domain within 15 minutes gives the stored result. Not a security audit.

Input Schema

NameRequiredDescriptionDefault
freshNotrue: check again now.
domainYesLike example.com, no https:// or path.
mcp_urlNoIts MCP server if any: https on the same domain, like https://example.com/mcp.
passport_tokenNoYour amp_ token, only if you have no app sign-in and cannot send a header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "domain": "example.com",
+    "mcp_url": "https://example.com/mcp"
+  }
+]
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."New value: +"Your amp_ token, only if you have no app sign-in and cannot send a header."
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Discloses non-obvious behavior annotations cannot convey: at most 24 requests, one over plain http, up to 5 to the target's MCP server, no logins or form posts, and a 15-minute result cache per domain. This tells the agent the tool makes real outbound network calls and how much, and that a repeat call may return stale data.

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?

Front-loaded with the free/read-only framing and information-dense throughout; almost every clause carries a fact. The clipped fragments ('At most 24 requests, one over plain http') read telegraphically and take a second pass to parse, costing a point.

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?

With no output schema, the description carries the return burden and does so: each check yields pass, warn, fail or not checked, with fixes. Combined with the request budget, cache rule and no-auth/no-write guarantees, nothing needed to call it correctly is missing.

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?

Schema coverage is 100%, so baseline is 3, but the description adds real meaning: the 15-minute cache explains the purpose of `fresh`, and the 'up to 5 requests to its MCP server if it names one' explains what `mcp_url` triggers. `passport_token` is left entirely to the schema, which keeps it from a 5.

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?

States a specific verb and resource ('Reads a website's public facts') and then enumerates the exact dimensions checked: HTTPS/headers, certificate dates, SPF/DMARC, privacy/terms/contact pages, llms.txt, robots.txt, MCP labels. No sibling tool in the list does a comparable whole-site public-facts sweep, so an agent can place it immediately.

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?

'Free' plus 'Not a security audit' gives a clear inclusion signal and one explicit exclusion, which is more than most siblings offer. It stops short of naming the adjacent alternatives (verify_job_sites, prove_domain, uptime_add) that an agent might confuse it with.

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

All AgentMart toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources