Skip to main content
Glama

Take The Meeting

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. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already provide readOnly, openWorld, idempotent, and non-destructive hints, but the description adds substantial behavioral detail: USPTO PatentsView soft-fails after sunset, empty fda_products can be expected for non-biologic companies, sources_used/sources_failed distinguish real 'no data' from bugs, and names resolve via SEC EDGAR. This goes far beyond what annotations alone convey.

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?

The description is long but every sentence earns its place: trigger examples, routing instruction, source list, return-field expectations, failure semantics, and input edge cases. It is front-loaded with the most critical routing information before enumerating details, and the structure is logically organized.

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?

There is no output schema, so the description must explain return values and edge behavior itself; it does so thoroughly, covering each data source, the composition of the return object, sources_used/sources_failed, and private-company resolution failure. An agent has everything needed to invoke this tool correctly without additional inference.

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%, so the baseline is 3. The description's parameter-related content mostly restates the schema: both type values behave identically and value can be a ticker, CIK, or company name. It adds examples but no new semantic constraints, so it does not elevate the score above baseline.

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-phrase examples and defines the tool as a 'full cross-source profile of a US public company in ONE parallel call.' It clearly names the resource, verb, and scope, and implicitly differentiates from sibling tools like resolve_entity and compare_entities by emphasizing the holistic multi-source profile behavior.

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?

It explicitly says 'ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view,' giving a direct decision rule and naming the alternative approach. It also covers the private-company edge case, telling the agent to expect resolved:false with notes rather than a bare failure, which is important routing context.

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

All Take The Meeting 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.7/5.0
Disambiguation3/5

Most tools have distinct, well-documented roles, but the set includes two effectively identical routers (ask_pipeworx and ask_pipeworx_beta, with the latter explicitly matching the former right now) and a dense cluster of six Polymarket tools that an agent must read carefully to choose among. This is more than a minor overlap, though the detailed descriptions prevent it from being complete chaos.

Naming Consistency3/5

Everything is snake_case, which is a plus, but the patterns are inconsistent: some tools are verb_noun (resolve_entity, validate_claim, list_subscriptions), some are noun phrases (entity_profile, bet_research, recent_alerts), some use brand prefixes (ask_pipeworx*, polymarket_*, pipeworx_*), and take_the_meeting_evaluate is a sentence-like outlier. The prefixes do provide grouping, but the naming doesn't give a predictable action structure.

Tool Count2/5

32 top-level tools is above the 25+ threshold and will bloat an agent's tool-selection surface, especially because the server name 'Take The Meeting' suggests a narrow meeting tool while 31 of the tools are unrelated Pipeworx/data features. Even as a broad data-research server, several tools could be collapsed (the ask variants, the Polymarket family), so the count feels inflated.

Completeness2/5

For the purpose implied by the server name and the lone meeting tool, the surface is severely incomplete: there is no way to list or fetch meetings, access calendar/attendee context, or do anything beyond evaluating one set of supplied parameters. For the broad data-research domain that most tools actually serve, the read/research side is rich, but that is a completely different purpose from 'Take The Meeting', leaving the meeting feature as a disconnected dead end.

Resources