Skip to main content
Glama

Conceptnet

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").

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

The description richly details behavioral traits beyond the annotations: it fans out to multiple sources, has fallback mechanisms, accepts various date formats, and returns structured data with citation URIs. No contradictions with annotations (readOnly, idempotent). The soft-fail for patents is explicitly noted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with query examples and provides thorough context. While every sentence adds value, it is somewhat long. However, the structure is logical, moving from examples to behavior to alternatives.

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 (multiple sources, date windows) and the lack of an output schema, the description sufficiently explains what the tool returns (changes grouped by source, total_changes, citations). It also mentions the alternative tool for static profiles, making it complete for selection and invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds significant value: it explains the 'since' parameter accepts ISO dates or relative shorthand and recommends '30d' or '1m'. It clarifies 'value' accepts ticker or CIK, and 'type' is only 'company'. This goes beyond the schema's descriptions.

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 begins with concrete example queries and explicitly states it is a change feed for a company. It distinguishes itself from the sibling 'entity_profile' tool, which is for static profiles. The verb 'fan out' and listing of sources (SEC EDGAR, GDELT, USPTO) makes the action and resource very clear.

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?

The description provides explicit guidance on when to use this tool versus 'entity_profile' (static profile). It also explains internal fallback logic (GDELT preferred, GNews when rate-limited) and soft-fail behavior for USPTO. This gives clear context for expected behavior.

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

All Conceptnet 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.5/5.0
Disambiguation2/5

Several tools have heavily overlapping purposes: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-identical, and the five polymarket_* tools (arbitrage, edges, edge_tracker, fill_risk, kalshi_spread) all target prediction-market opportunities. The memory tools (remember/recall/forget) are distinct, as are subscriptions, but the routing and Polymarket clusters create real misselection risk.

Naming Consistency3/5

All names are snake_case, but the pattern is mixed: some are verb_noun (ask_pipeworx, compare_entities, discover_tools, resolve_entity), some are noun_verb or adjective_noun (bet_research, entity_profile, pipeworx_trending, recent_changes), and some are bare nouns/verbs (lookup, query, recall, relatedness). The 'polymarket_*' and 'ask_pipeworx*' families are consistent internally, but the overall set lacks a uniform verb-first convention.

Tool Count2/5

With 34 tools, the server is heavily over-scoped for a server named 'Conceptnet' — the vast majority of tools belong to a separate Pipeworx data-access product, not a semantic-network API. While each tool has a use, the count feels bloated and the server name misrepresents the actual surface.

Completeness4/5

The ConceptNet portion is complete (lookup, query, relatedness cover graph traversal). The Pipeworx portion is also fairly complete: universal router, grounded mode, deep research, entity profiles, comparisons, claim validation, subscription lifecycle, memory, and feedback. Minor gaps exist (e.g., no direct SEC filing fetch without going through ask_pipeworx), but the meta-tools mostly fill them.

Resources