Skip to main content
Glama

Server Details

Working Capital Quotes: the site's own MCP server — dataset, enquiry (enquiry = a human handoff,...

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A3.6/5.0

Scored across 10 tools

Disambiguation4/5

The dataset_* family splits cleanly by query shape: schema, provenance, exact row match, substring search, aggregates, top-N, and multi-value 'X vs Y' comparison. The only soft spots are dataset_row vs dataset_search vs dataset_compare, which all retrieve rows and differ only by match semantics, and slight duplication between dataset_columns and dataset_provenance (both mention the provenance banner).

Naming Consistency4/5

The seven dataset tools use a clean, uniform dataset_<operation> pattern, and the enquiry tools are readable and predictable. The minor deviation is that enquiry_describe/enquiry_fields are noun-prefixed while submit_enquiry is verb-prefixed, so the enquiry group doesn't share one single convention.

Tool Count5/5

Ten tools is well within a healthy range and each one earns its place: six read/query tools covering distinct access patterns and three enquiry tools covering the describe-fields-submit lifecycle. Nothing looks redundant or padded.

Completeness4/5

The read surface covers schema discovery, provenance/attribution, exact and fuzzy lookup, aggregates, rankings, and comparisons, and the enquiry flow (describe, fields, two-step submit with consent) is fully specified. Gaps are minor: no range/date filtering or group-by beyond 'compare', and no way to check the status of a submitted enquiry.

Available Tools

10 tools
dataset_columnsDataset columns and shapeAInspect

The columns, which of them are numeric, the row count and the provenance banner of the Working Capital Quotes dataset. Call this first to learn the schema.

Inputs: no named parameters.

dataset_compareCompare rows side by sideCInspect

The rows of the Working Capital Quotes dataset whose column is any of the given values, in the order given, for "X vs Y" questions.

Inputs: column (required), values (required).

dataset_provenanceWhere this data comes from, and how to cite itAInspect

The source, the date it was computed, the licence and the citation for the Working Capital Quotes dataset. Read this to attribute a figure correctly.

Inputs: no named parameters.

dataset_rowLook a row up by an exact keyBInspect

The rows of the Working Capital Quotes dataset where a column equals a value exactly (case-insensitive).

Inputs: value (required), column (required).

dataset_statsSummary statistics for a numeric columnBInspect

count, min, max, mean, median and sum of a numeric column of the Working Capital Quotes dataset (grouping commas and currency are handled; non-numeric rows are excluded and counted).

Inputs: column (required).

dataset_topRank rows by a numeric columnBInspect

The highest (or lowest) rows of the Working Capital Quotes dataset by a numeric column: "which is the most/least X".

Inputs: column (required), limit, ascending.

enquiry_describeWhat you get: an ENQUIRY with a human (not a purchase, not a guaranteed quote)AInspect

Read first. States plainly what submit_enquiry does on Working Capital Quotes: it starts an enquiry with human providers who quote directly. Nothing is bought, ordered or paid; no quote is guaranteed; it is free. Also returns who receives the details, the consent wording, and how the person confirms.

Inputs: no named parameters.

enquiry_fieldsThe questions the enquiry asksAInspect

Every field of the Working Capital Quotes enquiry: key, label, type, whether required, help text and the allowed options where there are any. Pass answers to submit_enquiry keyed by field key.

Inputs: no named parameters.

submit_enquirySubmit an ENQUIRY to human providers (two steps; not a purchase)AInspect

Submits an enquiry to Working Capital Quotes: NOT a purchase, NOT a guaranteed quote. Step 1: call with the answers (keyed by field key from enquiry_fields) and consent=true; it validates and returns a summary, the consent line and a confirmation token; show the person the summary and the consent line. Step 2: only if the person agrees, call again with the same answers, consent=true and the confirmation token; the enquiry is then submitted, and the person receives an email with a link they must click before any provider sees it. Consent means the person has read and agreed to: "By sending this you agree the Working Capital Quotes team reads your enquiry and replies by email. We do not pass it to anyone else."

Inputs: answers (required), consent (required), confirmation.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables AI assistants to match users with capital providers for business loans, real estate, and asset tokenization through a conversational intake process.
      MIT
    • F
      license
      B
      quality
      D
      maintenance
      MCP server for paid business data services with free previews and paid tools (enriched search and competitive analysis) using x402 payment flow via Pyrimid Protocol on Base.
      5
      -
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources