Skip to main content
Glama

Companies House

by io.github.pipeworx-io

Recent Changes

recent_changes
Read-onlyIdempotent

"What's new with X" / "latest on Y" / "what happened to Z this week / month / quarter" / "updates on Acme" / "news on Tesla recently" / "what's happening with Apple" — change feed for a company in the last N days/weeks/months in ONE parallel call. Fans out to SEC EDGAR (filings since since), GDELT→GNews fallback (news mentions in window — GDELT preferred, GNews when rate-limited or 5xx), USPTO (patents granted; PatentsView API sunset May 2025 so this soft-fails until reactivated). since accepts ISO date ("2026-04-01") or relative shorthand ("7d", "30d", "3m", "1y"). Returns structured changes[] grouped by source + total_changes count + pipeworx:// citation URIs. Use entity_profile instead when you want the static profile (filings + fundamentals + LEI + patents) regardless of window.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesEntity type. Only "company" supported today.
sinceYesWindow start — ISO date ("2026-04-01") or relative ("7d", "30d", "3m", "1y"). Use "30d" or "1m" for typical monitoring.
valueYesTicker (e.g., "AAPL") or zero-padded CIK (e.g., "0000320193").

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds rich detail: fans out to SEC EDGAR, GDELT→GNews fallback, USPTO soft-fail, and structured output with citations. 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?

Front-loaded with example queries, each sentence adds value: sources, param details, sibling distinction. No fluff; dense but clear.

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?

Given the tool's complexity (multi-source, fallback, soft-fail) and no output schema, the description covers all essential aspects: input params with examples, output structure, limitations, and sibling differentiation. Exceptionally complete.

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. The description adds value beyond schema by providing recommended defaults (e.g., "30d" for since) and clarifying that value accepts tickers or CIK. This extra guidance earns a 4.

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 it provides a change feed for a company over a recent window, with specific verbs like "what's new" and "latest on". It distinguishes from sibling entity_profile which is for static profiles.

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

Usage Guidelines5/5

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

Explicitly states when to use (for recent change queries) and provides a direct alternative: 'Use entity_profile instead when you want the static profile'. Also gives example query forms.

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

All Companies House 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 have overlapping jobs: ask_pipeworx_beta is currently identical to ask_pipeworx, ask_pipeworx_grounded is the same router with stricter extraction, and discover_tools/suggest_questions both serve discovery. Company-facing tools also overlap (entity_profile vs recent_changes vs compare_entities), so an agent could easily route a query to the wrong tool despite detailed descriptions.

Naming Consistency3/5

Names are mostly snake_case and grouped prefixes like get_*, ask_pipeworx*, and polymarket_* are readable. However, conventions are mixed across the set: some are verb_noun (search_companies), some are noun phrases (entity_profile, deep_research, recent_changes), and the Companies House family sits awkwardly beside unrelated Pipeworx and prediction-market families.

Tool Count1/5

With 36 tools, the server is already heavy, but only five tools actually serve the named Companies House domain. The other 31 belong to Pipeworx querying, memory, subscriptions, and Polymarket trading, which is a severe mismatch between the server's stated purpose and its actual surface.

Completeness3/5

For UK company data, the core surface is mostly covered: search, company profile, filings, officers, and PSCs. However, charges and official document retrieval are missing even though get_company links to them, and the unrelated tools do nothing to complete the Companies House domain.

Resources