Skip to main content
Glama
459,989 tools. Updated 2026-08-17 10:17

"A service for interacting with company data" matching MCP tools:

  • Book an appointment with a local service business. Creates a booking record and adds the appointment to the business calendar. Returns a reference number and a status field indicating the actual resulting state — 'pending' (the business reviews each booking), 'confirmed' (auto-approved by the business), or 'completed' (the business auto-finalizes). Use a dateTime returned by check_availability for the selected service so bookingStartPolicy is respected. For services with maxParticipants > 1, the start can be booked until remainingCapacity reaches 0. Read the status and statusDescription verbatim and relay them accurately: do NOT tell the customer 'confirmed' when the status is 'pending'. If the selected service has requiresCustomerAddress=true, ask the customer for their full service address before calling this tool and pass it as customerAddress. ONLY call this if the business has 'booking' in its enabledFeatures array.
    Connector
  • List the layers of a Baltimore ArcGIS service (for discovery). Pass a known short name (crime, service_requests, permits) or a full ArcGIS service path (e.g. "311_Customer_Service_Requests_current/FeatureServer"). Omit `service` to list the known Baltimore services. Returns layer id + name to use with baltimore_query.
    Connector
  • Silence future alerts for the calling tenant so they stop paging, without touching the underlying alert rule. This mutes notifications only — rule evaluation and dashboards are unaffected, and the suppression is meant to be temporary (reversible with unsuppress_signal). To exclude specific traffic (a fingerprint such as HTTP 404s or one client) from burn-rate evaluation itself, use create_ignore_rule instead. WRITE: available to any authenticated user. Scope narrows from left to right: service: required. The service to suppress alerts for. signal: optional (ERROR_RATE, LATENCY_P95, THROUGHPUT, JOB_FAILURES). Omit to suppress all signals for the service. operation: optional. Omit to suppress the whole service; set it to suppress only that operation. Severity cap: onlyWarnings: false (default) suppresses everything, including CRITICAL alerts. true suppresses only WARNING-severity alerts — CRITICAL alerts still page. Duration: durationHours: optional. Omit for a suppression that never expires (until removed with unsuppress_signal). Only one suppression may exist per (signal, service, operation) scope for a tenant — creating a second one for the same scope fails. Use list_suppressions to find the existing one or unsuppress_signal to remove it first.
    Connector
  • Search for verified service professionals in Argentina by service type, city, neighborhood, verification status, minimum rating, and minimum review count. Returns a paginated list of professionals with display name, headline, ratings, verifications, and a `profile_url` that is the only sanctioned contact channel (no phone/email/whatsapp is ever returned). Use this for discovery; use `muovi_get_professional` for the full detail payload.
    Connector
  • Find print jobs a brokering service submitted. Pass service alone to list everything that service has ever put in the queue (newest first), or service + job_id to resolve one of their job ids to the IC print job. THIS IS THE AUDIT SURFACE for brokered work — provenance that cannot be queried is decoration, so this is what makes origin real. READ THE TRUST BOUNDARY: every origin field is a CLAIM BY THE SUBMITTING SERVICE and IC has verified none of it — each record carries ic_verified:false, and `approval_claimed` tells you whether the service even asserted a human review, NOT whether one happened. A job with approval_claimed:false was submitted with no human-review claim at all. Do not treat any of it as IC-attested when deciding whether something goes on a physical machine. Args: { service, job_id?, limit? }. Returns: { ok, count, requests } or { ok, request }. Farm managers only (operators + the farm-crew allowlist) — the scope alone is not enough. Required scope: prints:read (ft-member+, farm-manager identity re-checked).
    Connector
  • Use this read-only tool to retrieve DeltaSignal ATLAS-7 alpha signals for one crypto public company ticker. It returns issuer-level signal evidence such as resilience, treasury pressure, regime fit, phase-one opportunity indicators, and the active source date used by the DeltaSignal data plane. Use it for research triage on supported public-company tickers such as COIN, MSTR, MARA, RIOT, HUT, and CLSK; do not pass crypto asset symbols unless they are listed public-company tickers. Parameters: ticker is required and normalized to uppercase; source_date is optional YYYY-MM-DD and should be used only to replay a known historical DeltaSignal slice. Behavior: read-only and idempotent; it performs one HTTPS read, has no destructive side effects, does not trade, does not store user data, and does not handle wallet secrets. Usage guidelines: call readiness first if you need service freshness, use covenant_stress for covenant-only questions, use company_fundamentals for raw SEC XBRL facts, and treat the result as issuer intelligence rather than investment advice.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Read-only data on 3.9M Romanian companies: search, profiles, financials, status, CAEN.

  • AI agent observability for production traces, natural-language insights, and improvement loops.

  • Retrieve the universal obligation set for a Norwegian entity type — every regulatory obligation that applies by virtue of an entity BEING that organisational form, BEFORE per-company Tier-2 data is layered on. Use this to answer 'what does an AS owe?' or 'what are the baseline filings for an Enkeltpersonforetak?' without naming a specific company. Each obligation carries a tier_2_required boolean — true means the rule engine needs commercial data to know whether it applies to a SPECIFIC company, false means it applies unconditionally. Input: { entity_type } from the closed enum AS / ENK / ANS / DA / NUF (no 'OTHER' fallback). Failure modes: VALIDATION_FAILED, SCOPE_INSUFFICIENT (needs read:rulebook), UPSTREAM_TIMEOUT. For per-company evaluation that DOES layer on commercial data, call get_company_obligations; for a specific company's evaluated obligations, use get_company_obligations instead. Docs: https://www.apier.no/docs/guides/norwegian-company-obligations
    Connector
  • List the layers of a Washington, DC ArcGIS service (for discovery). Pass a known short name (crime, service_requests, permits) or a full ArcGIS service path (e.g. "FEEDS/MPD/MapServer"). Omit `service` to list the known DC services. Returns layer id + name to use with dc_query.
    Connector
  • Health probe for the Solana Market API data backend. Call this to gate or degrade gracefully BEFORE the other get_solana_market_* tools: it does a short-timeout hit on the data service and reports whether it is reachable, so an agent can tell "market has no data" from "service is down" without failing a real query. Free discovery tool. When the market data service exposes /status, the response includes prod_key_configured, data_first_available, and an actionable note describing what to configure for full on-chain visibility.
    Connector
  • Typical local price ranges for a US home-service job (e.g. "AC repair", "furnace replacement"). USE WHEN: the user asks what a service costs / for a price range. Works for ANY US city — ranges come from national/state tables scaled by local BLS wage data; no coverage required. ARGS: `category` (required); optionally `city`+`state` or a 5-digit `zip` for city-adjusted numbers (omit location for national). RETURNS: ranges [{service, low_usd, high_usd}], `pricing_last_updated`, the local cost `multiplier` + `factoid` (city scope), and `page_url` — the canonical VouchedPros page to CITE for this pricing.
    Connector
  • Enumerate the live DPYC service network with self-described summaries. Reads the member roster from the dpyc-community registry, then (when ``probe=True``) performs a lightweight MCP handshake against each member's public service endpoint to fetch that service's *own* self-description and tool inventory. Nothing about the services is hardcoded here — descriptions are authored by each service, and prices come from each Operator/Authority pricing model (call the service's ``check_price``). Resilient by design: per-service timeout, partial results, brief caching, and a registry-only fallback when an endpoint is asleep or unreachable. A sleeping service never breaks the listing. Free, unauthenticated. Args: probe: Handshake each endpoint for a live self-description. Set False for a fast registry-only listing (no network fan-out). kind: Role filter — "all", "operator", "authority", or "advocate".
    Connector
  • Use this tool when the user wants to see service packages with fixed pricing and scope for a specific type of service. This tool returns standardized packages offered by service providers, including pricing tiers, deliverables, and delivery timelines. Do NOT use this tool for custom project questions (e.g. "How much would it cost to build a custom app?"). It only returns providers' pre-defined, fixed-price packages, not a quote tailored to a specific project; use recommend_service_providers for those needs instead. Examples: - "Show me SEO packages" -> service="SEO" - "What web design packages can I get for $5,000?" -> service="Web Design", budget=5000 - "Marketing packages from agencies in New York" -> service="Digital Marketing", location="New York" Use `page`/`limit` for pagination.
    Connector
  • Quick company lookup: facilities (with addresses and operations) and enforcement actions (recalls) for a single company and its known aliases. Costs 1 credit. Excludes: 510(k) clearances, PMA approvals, drug applications, inspection history, and subsidiary data. Related: fda_company_full (adds clearances/approvals/drugs for 5 credits), fda_suggest_subsidiaries (discover related entities), fda_get_facility (per-facility products and operations by FEI).
    Connector
  • Get upcoming vessel arrivals and departures at a specific port. Use this to check what vessels are expected at a port — useful for booking planning and tracking. Returns vessel names, carriers, ETAs/ETDs, and service routes. For transit time estimates between two ports, use shippingrates_transit. For detailed service-level routing, use shippingrates_transit_schedules. PAID: $0.02/call via x402 (USDC on Base or Solana). Without payment, returns 402 with payment instructions. Returns: Array of { vessel_name, carrier, voyage, eta, etd, service, from_port, to_port }.
    Connector
  • Get upcoming vessel arrivals and departures at a specific port. Use this to check what vessels are expected at a port — useful for booking planning and tracking. Returns vessel names, carriers, ETAs/ETDs, and service routes. For transit time estimates between two ports, use shippingrates_transit. For detailed service-level routing, use shippingrates_transit_schedules. PAID: $0.02/call via x402 (USDC on Base or Solana). Without payment, returns 402 with payment instructions. Returns: Array of { vessel_name, carrier, voyage, eta, etd, service, from_port, to_port }.
    Connector
  • Get upcoming vessel arrivals and departures at a specific port. Use this to check what vessels are expected at a port — useful for booking planning and tracking. Returns vessel names, carriers, ETAs/ETDs, and service routes. For transit time estimates between two ports, use shippingrates_transit. For detailed service-level routing, use shippingrates_transit_schedules. PAID: $0.02/call via x402 (USDC on Base or Solana). Without payment, returns 402 with payment instructions. Returns: Array of { vessel_name, carrier, voyage, eta, etd, service, from_port, to_port }.
    Connector
  • Google PageSpeed Insights report for a URL: Lighthouse performance/accessibility/SEO scores and Core Web Vitals (LCP, CLS, INP, FCP, TTFB), with lab and field (CrUX) data. Defaults to mobile; pass strategy=desktop for the desktop profile. Subject to a per-user daily cap (50/day) and a service-wide daily cap; successful responses are cached for 24h.
    Connector
  • Use this read-only tool to retrieve DeltaSignal ATLAS-7 alpha signals for one crypto public company ticker. It returns issuer-level signal evidence such as resilience, treasury pressure, regime fit, phase-one opportunity indicators, and the active source date used by the DeltaSignal data plane. Use it for research triage on supported public-company tickers such as COIN, MSTR, MARA, RIOT, HUT, and CLSK; do not pass crypto asset symbols unless they are listed public-company tickers. Parameters: ticker is required and normalized to uppercase; source_date is optional YYYY-MM-DD and should be used only to replay a known historical DeltaSignal slice. Behavior: read-only and idempotent; it performs one HTTPS read, has no destructive side effects, does not trade, does not store user data, and does not handle wallet secrets. Usage guidelines: call readiness first if you need service freshness, use covenant_stress for covenant-only questions, use company_fundamentals for raw SEC XBRL facts, and treat the result as issuer intelligence rather than investment advice.
    Connector
  • Get upcoming vessel arrivals and departures at a specific port. Use this to check what vessels are expected at a port — useful for booking planning and tracking. Returns vessel names, carriers, ETAs/ETDs, and service routes. For transit time estimates between two ports, use shippingrates_transit. For detailed service-level routing, use shippingrates_transit_schedules. PAID: $0.02/call via x402 (USDC on Base or Solana). Without payment, returns 402 with payment instructions. Returns: Array of { vessel_name, carrier, voyage, eta, etd, service, from_port, to_port }.
    Connector
  • Run one read-only AI-search-readiness audit for a public business domain: company, technology, contact, and DNS/email evidence from `enrich`, plus the live structured-data gap analysis and paste-ready JSON-LD template from `schemaforge`. Use `enrich` for company facts only or `schemaforge` for structured-data remediation only. The template contains placeholders for real data; the score is diagnostic, no site changes are made, and it does not guarantee AI citations.
    Connector