Skip to main content
Glama
203,652 tools. Last updated 2026-06-14 20:25

"Analyzing Large Amounts of Text" matching MCP tools:

  • USE THIS TOOL WHEN you have a known Act / SI and want the structural table of contents (parts, chapters, sections, schedules). Returns structural elements with XML id and title, e.g. 'section-47: Definitions'. AFTER calling, pass the numeric section identifier (use '47', NOT 'section-47') into legislation_get_section for full text. Large statutes (Companies Act 2006 has many hundreds of items) are paginated via offset/limit. Check has_more and total_items. Alternative: call read_resource(uri="legislation://{type}/{year}/{number}/ toc") for the full TOC as a newline-separated `id: title` string (no pagination). Use this tool when you need the structured response with offset / limit / has_more for stepping through large statutes.
    Connector
  • Fetch a specific public FTIR analysis result by ID. USE WHEN: - User provides a result ID (e.g., "result:12345" or "12345") - Following up on search to get full details - User shares a result number and wants details DO NOT USE: - For searching by keyword (use search) - For analyzing new spectra (use search_ftir_library) INPUT: - id: result identifier in format "result:<number>" or just "<number>" OUTPUT: - id: canonical result ID - url: direct link to result page - title: result headline - text: analysis summary - report_view: detailed analysis data - metadata: additional information EXAMPLE: >>> fetch(id="result:12345") >>> fetch(id="12345")
    Connector
  • Opens a live Trident document and returns its full contents as Trident markup DSL — the human-readable text format used to author diagrams. Use this to READ and UNDERSTAND the diagram: its structure, labels, connections, and layout. Do NOT rely on this to enumerate entity IDs for programmatic use — the DSL can be very large and the output may be truncated. To get a complete, structured list of all entity IDs and counts, use get_document_summary instead. Requires a valid access token.
    Connector
  • Fetch the next page of a large tool response. Use the nextCursor from _pagination in a previous response. This tool loads data into the context window — prefer the artifact download URL when available.
    Connector
  • Get a compound's default 3D conformer — atomic coordinates and bonds — for one CID. format="json" (default) returns parsed atoms and bonds the model can reason over directly; format="sdf" returns the raw V2000 SDF text for passthrough to docking, rendering, or conformer tools. Optionally lists alternate conformer IDs. Not every compound has computed 3D coordinates (large molecules, mixtures, and some salts do not).
    Connector
  • Use this before doing arithmetic on any amount typed by an Argentine user. Parses an Argentine peso amount string — e.g. '$1.234,56', '1234,56', '5.000', '5k' — into a plain number. Handles the Argentine convention where '.' is the thousands separator and ',' is the decimal separator. Also understands k/K suffixes ('5k' → 5000). Returns the parsed number and a normalised display string, or an error if the input cannot be parsed (null result, no number found, or zero). Always call this before operating on amounts received as text from chat or forms.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Release a partial payment for proof-of-attempt and refund the remainder. This is a two-step operation: 1. Release X% to the worker (reward for attempting the task) 2. Refund (100-X)% to the agent Common use case: Worker attempted the task but couldn't fully complete it. Default is 15% release for proof-of-attempt. Args: params: task_id, release_percent (1-99, default 15%) Returns: Both transaction results with amounts.
    Connector
  • List direct children of a backbone taxon — genera within a family, species within a genus, subspecies within a species. Paginated. Use gbif_match_species to get the taxonKey first, then iterate with offset for large groups.
    Connector
  • Fetch a specific filing's metadata and document content by accession number. Returns the primary document as readable text. Use offset/next_offset for multi-page access to large filings (10-K, S-1 can exceed 1M chars): pass the next_offset from a truncated response to read the next page. Use section to jump directly to a heading (e.g. 'risk factors', 'item 7') without needing an offset.
    Connector
  • USE THIS TOOL WHEN you have a known Act / SI and want the structural table of contents (parts, chapters, sections, schedules). Returns structural elements with XML id and title, e.g. 'section-47: Definitions'. AFTER calling, pass the numeric section identifier (use '47', NOT 'section-47') into legislation_get_section for full text. Large statutes (Companies Act 2006 has many hundreds of items) are paginated via offset/limit. Check has_more and total_items. Alternative: call read_resource(uri="legislation://{type}/{year}/{number}/ toc") for the full TOC as a newline-separated `id: title` string (no pagination). Use this tool when you need the structured response with offset / limit / has_more for stepping through large statutes.
    Connector
  • Edit a file in the solution's GitHub repo and commit. Two modes: 1. FULL FILE: provide `content` — replaces entire file (good for new files or small files) 2. SEARCH/REPLACE: provide `search` + `replace` — surgical edit without sending full file (preferred for large files like server.js) Always use search/replace for large files (>5KB). Always read the file first with ateam_github_read to get the exact text to search for. DEFAULTS TO `dev` BRANCH — writes don't touch prod. Use ateam_github_promote to ship dev→main when ready. Pass ref:'main' only for emergency hotfixes.
    Connector
  • List Power Automate flows in an environment. Returns id, displayName, state, triggerType, and lastModifiedTime for each flow. mode=owner (default): flows owned by the impersonated account, with full definition. mode=admin: all flows in the environment (requires an admin account). If search is provided, results are filtered to flows whose displayName contains the search text. For large environments pagination is time-bounded — if nextLink is returned, pass it as continuationUrl to retrieve the next batch.
    Connector
  • Get payment details needed to approve a task submission (Fase 1 mode). External agents use this to get the exact addresses and amounts they need to sign 2 EIP-3009 authorizations: one for the worker and one for the platform fee. Args: task_id: UUID of the task submission_id: UUID of the submission to approve Returns: JSON with worker_address, treasury_address, bounty_amount, fee_amount, token details, and signing parameters.
    Connector
  • Provides explanatory text for STRING features and limitations. Use this tool when the user question involves: - What is STRING is or how to use the tool (how_to_use_string, cytoscape) - functionality not available via MCP tools (e.g. GSEA, regulatory networks, large datasets). - meaning of the lines in the network (line_colors)
    Connector
  • Poll the status of a transcode or convert job. Call every 5 seconds until status is 'complete' or 'failed'. Status 'queued' or 'processing' is normal — large files take 5–15 minutes. Keep polling indefinitely until a terminal status is reached. Do not stop polling after a fixed number of attempts.
    Connector
  • Estimates litigation exposure risk for CHROs by analyzing past employee lawsuits, settlement amounts, and industry benchmarks. Inputs include company location, industry code, and employee count range. Returns exposure score, average settlement amounts, lawsuit frequency trends, and risk factors. Ideal for legal risk assessment, HR strategy planning, and board-level reporting. Pass async:true to avoid timeout.
    Connector
  • Look up locations for up to 100 IP addresses at once. Returns geolocation and ISP data in the same order as input. Use for analyzing multiple IPs efficiently.
    Connector
  • Read-only full-text search over message history in the active space. Use this to find prior discussion, decisions, or links instead of paging through messages(check). Narrow large result sets with channel, sender_type, or date_from/date_to, and page with limit/offset. Returns matched messages with sender and timestamp; it never modifies any state.
    Connector
  • Get order status by UUID. Aliases: get_order_status, check_order, order_status, order_details, fetch_order. Check the status and fill details of an existing order by its UUID. Returns current status (PENDING/FILLING/FILLED/PARTIAL/FAILED/CANCELLED), fill amounts, provider used, on-chain delegation tx hash if delivered. Use this to poll order progress after creating an order. Auth required (API key).
    Connector