EvalsInIDEServer

endpoint

https://api.galileo.ai/mcp/http/mcp

protocol

http-sse ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is EvalsInIDEServer live?

Yes — it answered the hub's last check (checked 5h ago). It answered 100% of checks over the last 30 days.

Is EvalsInIDEServer free to use?

Yes — the hub reached it with no key and no payment.

What tools does EvalsInIDEServer have?

13 tools: integrate_galileo_with_langchain, integrate_galileo_with_openai, get_logstream_insights, setup_galileo_experiment, get_code_remediation, get_signal_evidence_span, get_signal_evidence_context, create_prompt_template, ….

Is EvalsInIDEServer safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• integrate_galileo_with_langchain reads unknown never probed

  Integrate Galileo observability into LangChain applications. **Supported Languages:** python **Parameters:** - language (optional): Programming language for integration guide. Defaults to "python". **Provides:** - Complete integration code examples and setup instructions - Automatic logging of prompts, responses, model parameters, and token usage - Environment configuration templates - Language-specific best practices Returns working code snippets ready to copy and paste for robust LLM observability.

  mcp-tool

  12345678910111213

  {
    "type": "object",
    "title": "integrate_galileo_with_langchainArguments",
    "required": [
      "language"
    ],
    "properties": {
      "language": {
        "type": "string",
        "title": "Language"
      }
    }
  }

  arguments 13 lines copy
• integrate_galileo_with_openai reads unknown never probed

  Integrate Galileo observability into OpenAI API applications. **Supported Languages:** python, typescript **Parameters:** - language (optional): Programming language for integration guide. Defaults to "python". **Provides:** - Complete integration code examples and setup instructions - Automatic logging of prompts, responses, model parameters, and token usage - Environment configuration templates - Language-specific best practices Returns working code snippets ready to copy and paste for robust LLM observability.

  mcp-tool

  12345678910111213

  {
    "type": "object",
    "title": "integrate_galileo_with_openaiArguments",
    "required": [
      "language"
    ],
    "properties": {
      "language": {
        "type": "string",
        "title": "Language"
      }
    }
  }

  arguments 13 lines copy
• get_logstream_insights reads unknown 28h ago

  Get the insights (also known as signals) for a log stream in a specific project. This tool analyzes log streams and provides insights/signals that identify issues, patterns, and suggest improvements. **When to use this tool:** - User asks for "insights" or "signals" about a log stream - User mentions a project name and wants to analyze a log stream - User asks questions like: "What's wrong with my application?", "Get insights about my log stream", "Show me signals for my logs" **Parameters:** - project (required): The exact name of the Galileo project. Extract this from phrases like: - "in the {project} project" - "for project {project}" - "from {project}" Example: If user says "in the customer-support project", use project="customer-support" - log_stream (required): The exact name of the log stream. Extract this from phrases like: - "log stream {log_stream}" - "logs from {log_stream}" - "the {log_stream} log stream" - If user says "my log stream" without a name, ask them for the specific log stream name Example: If user says "about my log stream in customer-support", you may need to ask for the log stream name, or infer it from context **Example Natural Language Queries:** - "Get insights about my log stream in the customer-support project" → project="customer-support", log_stream={ask user or infer from context} - "Get insights for the api-logs log stream in customer-support" → project="customer-support", log_stream="api-logs" - "What insights do you have for my logs in project customer-support?" → project="customer-support", log_stream={ask user for specific log stream name} **Returns:** - A list of insights/signals about the log stream, including: - Issues and anomalies detected - Patterns and trends - Suggested improvements - Session notes and trace notes if available

  mcp-tool

  123456789101112131415161718

  {
    "type": "object",
    "title": "get_logstream_insightsArguments",
    "required": [
      "project",
      "log_stream"
    ],
    "properties": {
      "project": {
        "type": "string",
        "title": "Project"
      },
      "log_stream": {
        "type": "string",
        "title": "Log Stream"
      }
    }
  }

  arguments 18 lines copy
• setup_galileo_experiment reads unknown never probed

  Setup and create a Galileo experiment using the Galileo SDK. **Supported Languages:** python **Parameters:** - language (optional): Programming language for experiment setup guide. Defaults to "python". **Provides:** - Complete experiment setup code examples and instructions - Step-by-step guide for creating and running experiments - Dataset preparation and metrics configuration - Integration with existing application code - Advanced usage patterns for agentic/RAG workflows **What this tool helps you do:** - Set up Galileo experiments with datasets (remote or inline) - Create and configure prompts for experiments - Define custom metrics and use built-in scorers - Run experiments with proper logging and tracing - Integrate experiment workflows into existing applications - Inspect and analyze experiment results Returns working code snippets ready to copy and paste for robust experiment setup and execution.

  mcp-tool

  1234567891011

  {
    "type": "object",
    "title": "setup_galileo_experimentArguments",
    "properties": {
      "language": {
        "type": "string",
        "title": "Language",
        "default": "python"
      }
    }
  }

  arguments 11 lines copy
• get_code_remediation unknown 28h ago

  Read the selected Signal diagnosis and proposed code change by its existing IDs.

  mcp-tool

  1234567891011121314151617181920212223242526272829303132

  {
    "type": "object",
    "title": "get_code_remediationArguments",
    "required": [
      "project_id",
      "run_id",
      "signal_id",
      "remediation_id"
    ],
    "properties": {
      "run_id": {
        "type": "string",
        "title": "Run Id",
        "format": "uuid4"
      },
      "signal_id": {
        "type": "string",
        "title": "Signal Id",
        "format": "uuid4"
      },
      "project_id": {
        "type": "string",
        "title": "Project Id",
        "format": "uuid4"
      },
      "remediation_id": {
        "type": "string",
        "title": "Remediation Id",
        "format": "uuid4"
      }
    }
  }

  arguments 32 lines copy
• get_signal_evidence_span unknown never probed

  Read a cited span's input and output in 4,000-character pages under the caller's trace access policy.

  mcp-tool

  123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354

  {
    "type": "object",
    "title": "get_signal_evidence_spanArguments",
    "required": [
      "project_id",
      "run_id",
      "signal_id",
      "remediation_id",
      "occurrence_id",
      "span_id"
    ],
    "properties": {
      "run_id": {
        "type": "string",
        "title": "Run Id",
        "format": "uuid4"
      },
      "span_id": {
        "type": "string",
        "title": "Span Id",
        "format": "uuid4"
      },
      "signal_id": {
        "type": "string",
        "title": "Signal Id",
        "format": "uuid4"
      },
      "project_id": {
        "type": "string",
        "title": "Project Id",
        "format": "uuid4"
      },
      "input_offset": {
        "type": "integer",
        "title": "Input Offset",
        "default": 0
      },
      "occurrence_id": {
        "type": "string",
        "title": "Occurrence Id",
        "format": "uuid4"
      },
      "output_offset": {
        "type": "integer",
        "title": "Output Offset",
        "default": 0
      },
      "remediation_id": {
        "type": "string",
        "title": "Remediation Id",
        "format": "uuid4"
      }
    }
  }

  arguments 54 lines copy
• get_signal_evidence_context unknown never probed

  Read nearby spans in the cited trace and session under the caller's trace access policy.

  mcp-tool

  123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354

  {
    "type": "object",
    "title": "get_signal_evidence_contextArguments",
    "required": [
      "project_id",
      "run_id",
      "signal_id",
      "remediation_id",
      "occurrence_id",
      "span_id"
    ],
    "properties": {
      "after": {
        "type": "integer",
        "title": "After",
        "default": 3
      },
      "before": {
        "type": "integer",
        "title": "Before",
        "default": 3
      },
      "run_id": {
        "type": "string",
        "title": "Run Id",
        "format": "uuid4"
      },
      "span_id": {
        "type": "string",
        "title": "Span Id",
        "format": "uuid4"
      },
      "signal_id": {
        "type": "string",
        "title": "Signal Id",
        "format": "uuid4"
      },
      "project_id": {
        "type": "string",
        "title": "Project Id",
        "format": "uuid4"
      },
      "occurrence_id": {
        "type": "string",
        "title": "Occurrence Id",
        "format": "uuid4"
      },
      "remediation_id": {
        "type": "string",
        "title": "Remediation Id",
        "format": "uuid4"
      }
    }
  }

  arguments 54 lines copy
• create_prompt_template changes data unknown never probed

  Create a new global prompt template that can be used across all projects. **Prerequisites:** - Requires a valid Galileo API key configured in your MCP settings - You must have an active Galileo account with prompt template creation permissions **Required User Inputs:** Please ask the user to provide the following information: - name: A descriptive name for the prompt template. - template: The actual prompt template content. Can be plain text or JSON format for chat templates. **Optional User Inputs:** - raw: Boolean flag indicating if this is a raw template (default: false). - output_type: The expected output type for the template (optional). - model_alias: The model to use with this template (default: "gpt-4.1-mini"). - temperature: Controls randomness in the output (0.0 to 2.0, default: 0.7). - max_tokens: Maximum number of tokens in the response (default: 1000). - top_p: Controls diversity of the output (0.0 to 1.0, default: 1.0). - frequency_penalty: Penalty for frequent tokens (-2.0 to 2.0, default: 0.0). - presence_penalty: Penalty for repeated tokens (-2.0 to 2.0, default: 0.0). **Returns:** - Template ID for the created template - Template details including name, version, and settings - Success confirmation with template metadata **Example Tool Calls:** Simple text template: name="Customer Support Response",template="You are a helpful customer support agent. Please respond to the following customer inquiry: {inquiry}",model_alias="gpt-4.1-mini",temperature=0.5 JSON chat template: name="AI Coding Assistant",template="[{"role":"system","content":"You are an Extremely friendly and helpful AI Coding assistant"}]",model_alias="gpt-4.1-mini",temperature=0.3 **What this tool does:** 1. Authenticates using your Galileo API key 2. Creates a new global prompt template in your Galileo organization 3. Sets up the template with the specified settings and configuration 4. Returns the template ID and details for future use 5. Template will be available globally across all projects **Instructions for Agent:** Always ask the user to provide: name and template before making the tool call. These are required for successful template creation. The template will be created as a global template, accessible across all projects in the organization.

  mcp-tool

  1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677

  {
    "type": "object",
    "title": "create_prompt_templateArguments",
    "required": [
      "name",
      "template"
    ],
    "properties": {
      "raw": {
        "type": "boolean",
        "title": "Raw",
        "default": false
      },
      "name": {
        "type": "string",
        "title": "Name"
      },
      "top_p": {
        "type": "number",
        "title": "Top P",
        "default": 1
      },
      "template": {
        "type": "string",
        "title": "Template"
      },
      "max_tokens": {
        "type": "integer",
        "title": "Max Tokens",
        "default": 1000
      },
      "project_id": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Project Id",
        "default": null
      },
      "model_alias": {
        "type": "string",
        "title": "Model Alias",
        "default": "gpt-4.1-mini"
      },
      "output_type": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Output Type",
        "default": null
      },
      "temperature": {
        "type": "number",
        "title": "Temperature",
        "default": 0.7
      },
      "presence_penalty": {
        "type": "number",
        "title": "Presence Penalty",
        "default": 0
      },
      "frequency_penalty": {
        "type": "number",
        "title": "Frequency Penalty",
        "default": 0
      }
    }
  }

  arguments 77 lines copy
• get_signal_evidence unknown never probed

  Page stored occurrences for the selected Signal and its merged descendants.

  mcp-tool

  12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849

  {
    "type": "object",
    "title": "get_signal_evidenceArguments",
    "required": [
      "project_id",
      "run_id",
      "signal_id",
      "remediation_id"
    ],
    "properties": {
      "limit": {
        "type": "integer",
        "title": "Limit",
        "default": 20
      },
      "cursor": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Cursor",
        "default": null
      },
      "run_id": {
        "type": "string",
        "title": "Run Id",
        "format": "uuid4"
      },
      "signal_id": {
        "type": "string",
        "title": "Signal Id",
        "format": "uuid4"
      },
      "project_id": {
        "type": "string",
        "title": "Project Id",
        "format": "uuid4"
      },
      "remediation_id": {
        "type": "string",
        "title": "Remediation Id",
        "format": "uuid4"
      }
    }
  }

  arguments 49 lines copy
• validate_dataset reads unknown never probed

  Check the status of a synthetic dataset generation job and view dataset contents. This tool allows the user to check the progress of a synthetic dataset generation job that was previously started using the create_galileo_dataset tool. It always shows the first 10 rows of the dataset for preview, regardless of generation status. Users can start by asking a question such as: Check the status of my dataset generation job. **Parameters:** - dataset_id (required): The id of the dataset to check the generation status for. **Returns:** - The current status and progress of the synthetic dataset generation job, including progress message, steps completed, and total steps. - Always includes a preview of the first 10 rows of the dataset with column names and values, whether generation is complete, in progress, or failed. - Total number of rows in the dataset and how many are being shown. **Example:** After creating a dataset with create_galileo_dataset, use this tool to check if the generation is complete and preview the generated data.

  mcp-tool

  12345678910111213

  {
    "type": "object",
    "title": "validate_datasetArguments",
    "required": [
      "dataset_id"
    ],
    "properties": {
      "dataset_id": {
        "type": "string",
        "title": "Dataset Id"
      }
    }
  }

  arguments 13 lines copy
• create_galileo_dataset changes data unknown never probed

  Create a new Galileo dataset with multiple data source options. **Prerequisites:** - Requires a valid Galileo API key configured in your MCP settings - You must have an active Galileo account with dataset creation permissions **Creation Options:** Ask the user which option they prefer: 1. Synthetic data generation: Automatically generate data based on description 2. CSV file: Provide CSV content to create dataset (columns: input, output, optional metadata) 3. JSON data: Provide structured JSON data **Required User Inputs:** Please ask the user to provide the following information: - description: A description of the dataset they want to create. This will be used as instructions for the synthetic data generation if the user chooses to use the synthetic data source type. - data_source_type: The type of data source to use for the dataset. Valid types: "synthetic", "csv", "json". **Optional User Inputs:** - model: The model to use for generating synthetic data (e.g., "gpt-4.1-mini", "claude-4-sonnet"). - count: Number of synthetic samples to generate (must be between 1 and 100). - data_types: Types of data to generate. Valid types: "General Query", "Prompt Injection", "Off-Topic Query", "Toxic Content in Query", "Multiple Questions in Query". - sample_data: Sample data to use as reference during generation. Can be newline-separated examples. - csv_content: CSV file content as string (for CSV data source type). - json_data: JSON data as string or array of objects (for JSON data source type). - name: Name for the dataset (optional, defaults to "New Dataset"). **Returns:** - Dataset ID for the created dataset - Status of the generation job - Parameters used for generation - Next steps for accessing the dataset **Example Tool Call:** description="Generate customer service queries about product returns",model="gpt-4o-mini",count=20,data_types="General Query,Off-Topic Query",sample_data="How do I return a defective product? What is your return policy?" **What this tool does:** 1. Authenticates using your Galileo API key 2. Creates a new dataset in your Galileo organization 3. Dispatches a background job to generate synthetic data or processes uploaded data 4. Returns the dataset ID for tracking progress 5. Generated data will be available in your Galileo console **Instructions for Agent:** Always ask the user to provide: description and data_source_type before making the tool call. These are required for successful dataset creation. Ask the user to wait for the dataset to be created before using the validate_dataset tool. Continue to ask the user if they want to validate the dataset that was just created.

  mcp-tool

  12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182

  {
    "type": "object",
    "$defs": {
      "SyntheticDataTypes": {
        "enum": [
          "General Query",
          "Prompt Injection",
          "Off-Topic Query",
          "Toxic Content in Query",
          "Multiple Questions in Query",
          "Sexist Content in Query"
        ],
        "type": "string",
        "title": "SyntheticDataTypes"
      }
    },
    "title": "create_galileo_datasetArguments",
    "required": [
      "description"
    ],
    "properties": {
      "name": {
        "type": "string",
        "title": "Name",
        "default": "New Dataset"
      },
      "count": {
        "type": "integer",
        "title": "Count",
        "default": 10
      },
      "model": {
        "type": "string",
        "title": "Model",
        "default": "gpt-4.1-mini"
      },
      "json_data": {
        "type": "string",
        "title": "Json Data",
        "default": ""
      },
      "data_types": {
        "type": "array",
        "items": {
          "$ref": "#/$defs/SyntheticDataTypes"
        },
        "title": "Data Types",
        "default": []
      },
      "project_id": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Project Id",
        "default": null
      },
      "csv_content": {
        "type": "string",
        "title": "Csv Content",
        "default": ""
      },
      "description": {
        "type": "string",
        "title": "Description"
      },
      "sample_data": {
        "type": "string",
        "title": "Sample Data",
        "default": ""
      },
      "data_source_type": {
        "type": "string",
        "title": "Data Source Type",
        "default": "synthetic"
      }
    }
  }

  arguments 82 lines copy
• get_logstream_signals reads unknown never probed

  Get the signals (also known as insights) for a log stream in a specific project. This tool analyzes log streams and provides signals/insights that identify issues, patterns, and suggest improvements. **When to use this tool:** - User asks for "signals" or "insights" about a log stream - User mentions a project name and wants to analyze a log stream - User asks questions like: "What's wrong with my application?", "Get signals about my log stream", "Show me insights for my logs" **Parameters:** - project (required): The exact name of the Galileo project. Extract this from phrases like: - "in the {project} project" - "for project {project}" - "from {project}" Example: If user says "in the customer-support project", use project="customer-support" - log_stream (required): The exact name of the log stream. Extract this from phrases like: - "log stream {log_stream}" - "logs from {log_stream}" - "the {log_stream} log stream" - If user says "my log stream" without a name, ask them for the specific log stream name Example: If user says "about my log stream in customer-support", you may need to ask for the log stream name, or infer it from context **Example Natural Language Queries:** - "Get signals about my log stream in the customer-support project" → project="customer-support", log_stream={ask user or infer from context} - "Get insights for the api-logs log stream in customer-support" → project="customer-support", log_stream="api-logs" - "What signals do you have for my logs in project customer-support?" → project="customer-support", log_stream={ask user for specific log stream name} **Returns:** - A list of signals/insights about the log stream, including: - Issues and anomalies detected - Patterns and trends - Suggested improvements - Session notes and trace notes if available

  mcp-tool

  123456789101112131415161718

  {
    "type": "object",
    "title": "get_logstream_signalsArguments",
    "required": [
      "project",
      "log_stream"
    ],
    "properties": {
      "project": {
        "type": "string",
        "title": "Project"
      },
      "log_stream": {
        "type": "string",
        "title": "Log Stream"
      }
    }
  }

  arguments 18 lines copy
• search_docs reads unknown 28h ago

  Search across the Galileo documentation to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about Galileo, find specific documentation, understand how features work, or locate implementation details. The search returns contextual content with titles and direct links to the documentation pages. **Parameters:** - query (required): The search query to find relevant documentation. **Returns:** - Relevant documentation content and links based on the search query. **Example:** search_docs(query="how to set up data logging")

  mcp-tool

  12345678910111213

  {
    "type": "object",
    "title": "search_docsArguments",
    "required": [
      "query"
    ],
    "properties": {
      "query": {
        "type": "string",
        "title": "Query"
      }
    }
  }

  arguments 13 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.