Skip to main content
Glama

Doffin

by io.github.pipeworx-io

Entity Profile

entity_profile
Read-onlyIdempotent

"Tell me about X" / "research Acme" / "brief me on Tesla" / "what does Apple do" / "company profile for Microsoft" / "give me the rundown on NVDA" / "everything you know about $TICKER" — full cross-source profile of a US public company in ONE parallel call. ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view. Fans out across SEC EDGAR, XBRL, USPTO patents, federal contracts (USAspending), FDA-licensed biologics (Purple Book), H-1B hiring (DOL LCA), news and GLEIF, and returns: cik + company_name (+ resolved_from/resolved_to when value was a name); recent_filings (up to 5 with pipeworx://edgar/company/{cik}/filings/{accession} URIs); fundamentals (LATEST 10-K Revenues + NetIncomeLoss + Cash, sorted period_end DESC); patents (USPTO PatentsView API sunset May 2025 — soft-fails until reactivated); federal_contracts (USAspending awards where the company is the recipient); fda_products (FDA-licensed biologics — vaccines, cell/gene therapies — from the Purple Book; a company with only small-molecule/generic drugs will show none here, that is expected, not a failure); hiring (H-1B sponsorship volume + salary range from DOL LCA filings); recent news mentions via GDELT→GNews fallback; LEI via GLEIF. sources_used / sources_failed say which of these actually returned data for THIS company — an empty section is a real "no data", not a bug. Pass a ticker ("AAPL"), zero-padded CIK ("0000320193"), OR a company name ("Moderna") — names now resolve via SEC EDGAR's company-name match; a private company (no CIK/ticker) returns resolved:false with an explicit notes line, not a bare failure. type accepts "company" or "ticker" interchangeably — both take the same value shapes above.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYes"company" or "ticker" — both are accepted and behave identically; `value` can be a ticker, CIK, or company name either way. person/place coming soon.
valueYesTicker (e.g., "AAPL"), zero-padded CIK (e.g., "0000320193"), or company name (e.g., "Moderna") — names resolve via SEC EDGAR company-name match.

Schema Changelog

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

  1. Changed3 schema fields changed
    • changedInput schema / properties / type / description
      Previous value: -"Entity type. Only \"company\" supported today; person/place coming soon."New value: +"\"company\" or \"ticker\" — both are accepted and behave identically; `value` can be a ticker, CIK, or company name either way. person/place coming soon."
    • changedInput schema / properties / type / enum
      Previous value: -[
-  "company"
-]New value: +[
+  "company",
+  "ticker"
+]
    • changedInput schema / properties / value / description
      Previous value: -"Ticker (e.g., \"AAPL\") or zero-padded CIK (e.g., \"0000320193\"). Names not supported — use resolve_entity first if you only have a name."New value: +"Ticker (e.g., \"AAPL\"), zero-padded CIK (e.g., \"0000320193\"), or company name (e.g., \"Moderna\") — names resolve via SEC EDGAR company-name match."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the read-only/idempotent annotations, the description reveals substantial runtime behavior: parallel fan-out across multiple sources, per-source success/failure tracking via sources_used/sources_failed, news fallback (GDELT→GNews), patents soft-fail behavior, and resolution details like resolved_from/resolved_to. This gives the agent a strong mental model of what happens when the tool runs.

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 dense and slightly run-on, but every section contributes useful information for selecting and invoking the tool. It is front-loaded with purpose and usage guidance, and the detailed source/return lists are necessary given the lack of an output schema. It would be cleaner with bullet points, but it is not padded with filler.

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?

The definition covers input formats, supported sources, return sections, fallback behavior, no-data semantics, and edge cases like private companies. Since there is no output schema, the description carries the full burden of explaining return values, and it does so thoroughly. No critical operational information is missing.

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%, and the schema already documents both parameters thoroughly, including ticker/CIK/name formats and the interchangeable type semantics. The description largely repeats this information, adding only minor context like 'names now resolve via SEC EDGAR's company-name match,' which is already in the schema. 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 opens with concrete user phrasing and then states the core function: 'full cross-source profile of a US public company in ONE parallel call.' This clearly distinguishes the tool from siblings like resolve_entity and compare_entities, and the explicit preference over chaining single-source lookups reinforces its unique resource.

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 gives an explicit when-to-use rule: 'ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view.' It also explains how private companies are handled (resolved:false with a notes line), so the agent knows this tool is appropriate even for non-public entities and will not get a bare failure.

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

All Doffin 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
Disambiguation2/5

Several tool clusters have fuzzy boundaries: ask_pipeworx and ask_pipeworx_beta are described as currently identical, and ask_pipeworx/deep_research/validate_claim overlap for factual research. Polymarket_arbitrage, polymarket_edges, and bet_research also all surface betting opportunities, while ai_visibility_check and scan_competitor_ai_presence serve nearly the same purpose.

Naming Consistency3/5

Names are readable and mostly snake_case, but the pattern is mixed: doffin_* and polymarket_* use domain-prefixed nouns, ask_pipeworx* uses verb+product, and remember/recall/forget/subscribe are bare verbs. There is no single predictable verb_noun convention, though each internal cluster is somewhat consistent.

Tool Count2/5

34 tools is heavy for a server named Doffin, and only three tools actually relate to Norwegian procurement. The remaining surface is mostly general Pipeworx data access, prediction-market analysis, and memory utilities, which feels like several servers bundled under one misleading name.

Completeness3/5

For Doffin read-only access, search + recent + notice detail covers the core workflow well. However, the server's actual domain is fragmented across procurement, Pipeworx research, prediction markets, memory, and subscriptions, which makes coverage difficult to reason about and leaves minor gaps such as no subscription update capability.

Resources