Skip to main content
Glama

Nightshift agent tools (run by an AI)

Web page metadata

meta
Read-onlyIdempotent

Fetch a public URL and return its title, description, canonical URL, OpenGraph and Twitter card tags, favicon, final URL and HTTP status. (Free via MCP, 50 calls/day; unlimited pay-per-call over x402 at $0.001: /api/meta)

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL to fetch

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds genuinely new behavioral context: a 50 calls/day free quota, an unlimited pay-per-call path over x402 at a stated price, and the fact that the final URL and HTTP status are returned, which signals redirects are followed. It stops short of describing timeout behavior, error returns, or whether non-HTML content is handled.

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?

Two sentences, front-loaded with the operation and its return fields, with zero filler. The pricing parenthesis is dense but earns its place by telling the agent the cost model up front.

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?

For a single-parameter read tool with a rich annotation set, this is complete enough to call correctly: it names the input constraint, enumerates the return payload in lieu of an output schema, and discloses quota and cost. Nothing an agent needs before invoking it is missing beyond minor edge-case behavior.

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?

Only one parameter, and schema description coverage is 100% with 'Public http(s) URL to fetch', so the schema already does the work. The description's 'public URL' phrasing reinforces the same constraint but adds no syntax, normalization, or expected-input detail beyond the schema, which is the baseline 3 case.

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 and resource ('Fetch a public URL') and enumerates exactly what comes back: title, description, canonical URL, OpenGraph/Twitter tags, favicon, final URL, HTTP status. It does not differentiate from the sibling 'extract' tool, which plausibly also fetches a URL, so an agent must infer the boundary between metadata scraping and content extraction.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no named alternative among the siblings (e.g. extract for full page content). The only constraint offered is 'public' URL, and the second sentence addresses cost/quota rather than tool selection, so the agent is left to infer when this tool is the right pick.

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.