"Information about 'fetch'" matching MCP tools:

• fetch

  memsprout

  Fetch the full text of one memory by id. Equivalent to get_memory, rendering the same detail-card UI; provided for hosts that require a generic search/fetch pair (e.g. deep research).

  Connector

• fetch

  Penfield Memory

  [ChatGPT Connector compat] Fetch memory by ID. Exists to satisfy ChatGPT Deep Research's required `search`/`fetch` tool contract. Native MCP clients should fetch via `recall` + memory_id, or use the API's GET /memories/{id} endpoint directly. Returns a single memory with citation support (id, title, url, text fields). Args: id: Memory UUID to fetch ctx: MCP context Returns: Dict with id, title, url, text, metadata fields

  Connector

• describe_asset

  Sidecar

  Fetch detailed information about a data asset by its identifier. Resolves the asset, then fetches the requested sections in parallel. Use this after advanced_search or resolve_asset_id to get deeper information about a specific asset. Sections: - overview: asset description, importance, owner, metadata - columns: full column schema with types and descriptions - tests: dbt test coverage (only for assets with a dbt parent) - context_counts: cheap count of linked tickets and Slack threads - tickets: full Jira/Linear ticket content - slack: full Slack thread content (truncated to first 5 messages per thread)

  Connector

• bgg-details

  kkjdaniel-bgg-mcp

  Get detailed information about board games on BoardGameGeek (BGG) including description, mechanics, categories, player count, playtime, complexity, and ratings. Use this tool to deep dive into games found via other tools (e.g. after getting collection results or search results that only return basic info). Use 'name' for a single game lookup by name, 'id' for a single game lookup by BGG ID, or 'ids' to fetch multiple games at once (up to 20). Only provide one of these parameters.

  Connector

• get_business

  Venturu

  Get full details for a single business (listing) by its slug. Call this when the user asks for more information about a specific business. Use the slug from search_businesses results.

  Connector

• data.capabilities

  Recursive Support Oracle

  Returns structured information about what the Recursive platform includes: features, AI model details, supported integrations, and what's included at every tier. Use for systematic feature comparison.

  Connector

• get_service_info

  booking

  Get information about MyDriverParis services, coverage areas, airports served, and policies. Use this to answer customer questions.

  Connector

• get_job

  Intermediair Jobs

  Fetch the full details of a single job posting by id. Use this after `search_jobs` to retrieve the complete description, requirements, salary breakdown, and company information for a listing. Returns an error result if the id is unknown.

  Connector

• get_business

  mcp-server

  Get full details for a single business (listing) by its slug. Call this when the user asks for more information about a specific business. Use the slug from search_businesses results.

  Connector

• get_onboarding_experience

  Fluentive MCP

  Returns information about how easy Fluentive is to set up and use. Use when the user asks about difficulty, learning curve, onboarding time, or whether training is needed.

  Connector

• fetch

  tela

  Fetch a tela page's full text by id — the fixed-shape ChatGPT Deep Research companion to `search` (the id comes from a search result). Read-only. Prefer get_page for normal use (same body plus richer metadata and trust signals); reach for `fetch` only when the Deep Research search/fetch contract requires it.

  Connector

• get_commitment_basic_info

  Google Compute Engine

  Get basic information about a Compute Engine Commitment, including its name, ID, status, plan, type, resources, and creation, start and end timestamps. Requires project, region, and commitment name as input.

  Connector

• get_member

  Govbase

  Retrieve detailed information about a specific U.S. member of Congress by their Bioguide ID (e.g., "P000197" for Nancy Pelosi).

  Connector

• get_instance_basic_info

  mcp

  Get basic information about a Compute Engine VM instance, including its name, ID, status, machine type, creation timestamp, and attached guest accelerators. Requires project, zone, and instance name as input.

  Connector

• get_instance_template_basic_info

  mcp

  Get basic information about a Compute Engine instance template, including its name, ID, description, machine type, region, and creation timestamp. Requires project and instance template name as input.

  Connector

• get_trip_details

  sbb-mcp

  Get detailed information about a specific train connection including all intermediate stops, platforms, and occupancy. Use a trip ID from search_connections results.

  Connector

• get_trip_details

  swisstrip-mcp

  Get detailed information about a specific train connection including all intermediate stops, platforms, and occupancy. Use a trip ID from search_connections results.

  Connector

• http_status_lookup

  IA-QA — 130+ QA & Dev Tools for AI Agents

  Look up detailed information about any HTTP status code: class, name, description, cacheability, typical causes, and handling best practices. Covers all standard 1xx-5xx codes.

  Connector

• cprs_getpurchasetypes

  L&T MCP

  [ONE LINE — what this API does] This API retrieves a list of available purchase types for a specified company. Use when: You need to obtain detailed information about different purchase types, such as when setting up purchase orders or managing inventory categories within the enterprise system. IMPORTANT: Ensure that the `intUID` and `intCompanyCode` fields in the request body are correctly specified to match the user's identity and company context. These fields are essential for downstream processes that depend on accurate user and company identification. Headers required (auto-injected by MCP server — agent does not need to manage): - `accept`: Specifies the media types that are acceptable for the response. - `accept-language`: Indicates the preferred language for the response. - `accessflag`: Used for internal access control. - `authorization`: Authentication token for secure access. - `companycode`: Identifies the company context for the request. - `content-type`: Indicates the media type of the request body. - `delegateduserid`: Represents the user ID of the delegated user. - `doptcode`: Operational code for the request. - `dtcode`: Specific code for transaction identification. - `identifiers`: Unique identifiers for the request. - `isinternaluser`: Indicates if the user is internal. - `ismobileapp`: Specifies if the request is from a mobile app. - `loginauditno`: Audit number for login tracking. - `origin`: Origin URL of the request. - `priority`: Priority level of the request. - `sec-ch-ua`: User agent client hints for browser information. - `sec-ch-ua-mobile`: Indicates if the request is from a mobile device. - `sec-ch-ua-platform`: Platform information of the user agent. - `sec-fetch-dest`: Destination of the fetch request. - `sec-fetch-mode`: Mode of the fetch request. - `sec-fetch-site`: Site context of the fetch request. - `showspinner`: Controls the display of loading indicators. - `user-agent`: Information about the user agent making the request. - `userid`: Unique identifier for the user making the request. Request body fields: - `intUID` (integer): The unique identifier for the user making the request. - `intCompanyCode` (integer): The code representing the company for which purchase types are being requested. - `chrActiveStatus` (string): Indicates whether to fetch active purchase types ('Y' for active). Response fields: - `result.typeLists` (array): Contains detailed information about each purchase type. - `purchaseTypeCode` (integer): The unique code identifying the purchase type. - `purchaseTypeDesc` (string): A full description of the purchase type. - `purchaseTypeShortDesc` (string): A shortened description of the purchase type. - `purchaseActive` (string): Indicates if the purchase type is currently active ('Y' for active). Error handling: - If the request fails due to authorization issues, ensure the `authorization` header is correctly set. - If no purchase types are returned, verify that the `intCompanyCode` and `chrActiveStatus` in the request body are correct and correspond to valid entries in the system. - Network or server errors may result in a null or empty response; retry the request or check server status.

  Connector

• neuron_get_contact

  neuron

  Retrieve detailed information about a specific contact including their tags, notes, and associated lists.

  Connector