Skip to main content
Glama

Unphurl

by io.github.123Ergo

check_history

Read-onlyIdempotent

View recent URL check history. Shows what URLs have been checked, their scores, phishing status, and whether each check was free or used a pipeline credit.

Results are paginated. Use page and limit parameters to navigate. Default is 20 results per page, maximum 100.

History is retained for 90 days. Account-level stats (total credits, balance) never expire.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (default 1)
limitNoResults per page, max 100 (default 20)

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds valuable behavioral details: pagination behavior, 90-day retention, and the distinction between free checks and those using pipeline credits. This goes beyond what the annotations state.

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 three short paragraphs, front-loaded with the main purpose, followed by concise pagination and retention details. Every sentence provides useful information with no redundancy 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?

With no output schema, the description explains the return fields at a high level (URLs, scores, phishing status, free/credit) and covers pagination and retention. It lacks exact field names or sorting order, but is sufficient for a simple read-only list tool.

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%, with both 'page' and 'limit' fully documented including defaults and max. The description repeats this information ('Default is 20 results per page, maximum 100') without adding new semantic meaning beyond the schema, so a baseline 3 is appropriate.

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 clearly states 'View recent URL check history' with a specific verb and resource, and enumerates the fields shown (URLs, scores, phishing status, free/credit). This distinguishes it from sibling tools like check_url/check_urls which perform checks.

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?

The description provides clear context by explaining pagination (default 20, max 100) and the 90-day retention period, with a note that account stats never expire. While it doesn't explicitly name alternatives, it implies when to use this tool (for recent history) versus get_stats (for permanent account-level data).

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

All Unphurl toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation4/5

Most tools have clearly distinct purposes: check_url vs check_urls distinguish single vs batch, allowlist CRUD tools are separated, and profile management is distinct from account billing. Minor overlap exists between get_balance and get_stats (both report balance) and between list_profiles and show_defaults (both relate to scoring configuration), but descriptions clarify the differences.

Naming Consistency4/5

The vast majority of tools follow a verb_noun snake_case pattern (check_url, create_profile, list_allowlist, get_balance). A few outliers like purchase and signup are single verbs, but they are standard and do not break the overall predictability.

Tool Count4/5

18 tools is above the ideal 3-15 range but appropriate for the server's broad scope: URL analysis, custom scoring profiles, allowlist management, account billing, and reporting. Each tool serves a distinct function and none feel redundant or superfluous.

Completeness4/5

The tool surface covers the core domain thoroughly: single and batch URL checks, credit estimation, profile CRUD (create, list, delete, show defaults), allowlist CRUD, history, and account management (signup, balance, pricing, purchase). Minor gaps exist, such as no delete history or direct retrieval of a single past check by ID, but these are not critical.

Resources