Skip to main content
Glama

Uk Food Hygiene

by io.github.pipeworx-io

Recent Alerts

recent_alerts
Read-onlyIdempotent

Pull fired events from your subscription feed. Returns the most recent alerts the evaluator has written to your persisted feed — each carries source, citation_uri (pipeworx:// when available), and the raw event payload. Filter by type (e.g. "sec_8k") and/or since (ISO timestamp). Set mark_read:true to flag returned events read so the next call only shows newer ones. Polls work fine; the same feed is also at GET registry.pipeworx.io/alerts.json for scripts and dashboards.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoOptional — filter to one subscription type.
limitNoMax events to return (1-200, default 50).
sinceNoOptional ISO timestamp — return events fired_at >= this time.
mark_readNoFlag the returned events read in the same call (default false).
unread_onlyNoReturn only events where read_at is null (default false).

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true. Description adds behavior of mark_read parameter (flags events read, affecting subsequent calls) and response structure, which goes beyond annotations. No contradictions.

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?

Concise three sentences: first states core purpose, second details returned fields and parameter use, third adds polling suitability and alternative endpoint. No wasted words.

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?

Despite lacking output schema, description explains return structure (source, citation_uri, raw payload), covers all five parameters with usage context, and provides alternative access method, making it complete for agent decision-making.

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 has 100% parameter descriptions. Description adds value by explaining mark_read's effect on read-state management and clarifying that returned events include source, citation_uri, and raw payload, which informs parameter usage.

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?

Clearly states it pulls fired events from subscription feed, specifies returned fields (source, citation_uri, raw payload), and distinguishes itself from sibling tools like 'list_subscriptions' by focusing on recent alerts with read-state management.

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?

Provides context for polling ('Polls work fine') and mentions an alternative GET endpoint for scripts/dashboards. Implicitly suggests use for programmatic access with read-tracking, though lacks explicit when-not-to-use guidance.

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

All Uk Food Hygiene 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

A3.6/5.0
Disambiguation2/5

Several tools blur together: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all answer questions over the same data, and five polymarket_* tools overlap on edge detection and arbitrage. Descriptions help somewhat, but the boundaries are subtle and the server name 'Uk Food Hygiene' adds a layer of confusion.

Naming Consistency3/5

All names are lowercase snake_case, but conventions vary widely: brand-style names (ask_pipeworx, pipeworx_feedback), noun phrases (entity_profile, recent_changes), verb_noun pairs (list_subscriptions, validate_claim), and bare verbs (recall, forget). It is readable but does not follow one predictable pattern.

Tool Count1/5

A server named 'Uk Food Hygiene' has 33 tools, of which only two (uk_food_hygiene_search, uk_food_hygiene_details) relate to food hygiene. The rest are a grab-bag of Pipeworx platform utilities, prediction-market tools, memory helpers, and subscription features — an extreme mismatch between count and stated scope.

Completeness2/5

The two food hygiene tools cover search and detail lookup, which handles the core use case, but the broader tool surface has notable gaps: citation URIs are returned but no fetch/read tool exists, and the unrelated domains (prediction markets, company research, AI visibility) are deep in some places and absent in others. The overall surface feels like an incoherent collection rather than a complete domain toolkit.

Resources