Skip to main content
Glama

Insee

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.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint. Description adds valuable behavioral traits: parallel fan-out to SEC EDGAR, GDELT→GNews fallback, USPTO soft-fail due to API sunset, and return format. 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?

Description is comprehensive yet front-loaded with core purpose and examples. Every sentence adds value—covers data sources, fallbacks, parameter hints, and sibling differentiation. No redundancy.

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, fallbacks, soft-fail, relative dates) and no output schema, the description fully prepares the agent. Provides return structure, citation URIs, and links to sibling tool. Missing nothing essential.

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 description coverage is 100%. Description enhances semantics by explaining 'since' format with examples (ISO date and relative shorthand like '30d'), and clarifying 'value' can be ticker or CIK. Adds context beyond schema.

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 the tool provides a 'change feed for a company in the last N days/weeks/months' with specific verb ('change feed') and resource ('company'). It distinguishes from sibling 'entity_profile' by contrasting dynamic vs static data.

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?

Explicitly lists example use cases ('what's new with X', 'latest on Y') and directs to alternative 'entity_profile' for static profiles. Does not exhaustively describe when not to use, but the context is clear.

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

All Insee 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.9/5.0
Disambiguation3/5

Most tools have detailed, carve-out descriptions, but ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded share the same routing core, with the beta version currently identical to the stable one. The Polymarket and company-research clusters are better differentiated, but the number of overlapping research/query entry points still creates real selection risk.

Naming Consistency3/5

The set is consistently snake_case and has coherent prefixes like ask_pipeworx_ and polymarket_, but it mixes verb_noun names (resolve_entity, scan_dependency, discover_tools) with noun-phrase names (entity_profile, bet_research, recent_changes) and one-word verbs (remember, recall, forget). The naming is readable but does not follow one predictable pattern.

Tool Count2/5

With 32 tools, the server exceeds the 25+ threshold for too many tools and feels like a broad platform dump rather than a focused toolkit. Several utility, memory, and meta-discovery tools could reasonably live in separate servers, and the Insee name makes the breadth especially unfocused.

Completeness4/5

For the broad data-research platform it actually exposes, the coverage is strong: general lookup, grounded verification, deep research, entity resolution, company profiles, comparisons, change feeds, subscriptions, and memory all have working lifecycles. The main gap is that some unrelated utilities like scan_dependency and generate_llms_txt feel tacked on rather than part of a missing core workflow.

Resources