Get Experiment By Name
Return one caller-owned experiment by exact name.
Use this tool when the caller already knows the exact experiment name and wants the full experiment object. Name matching is exact and scoped to the authenticated user, so the route does not perform fuzzy lookup across other users’ experiments.
When to Use:
- Call this when the workflow is keyed by a user-provided experiment name rather than a stored ID.
- Call this when the caller needs the full experiment payload, not just the dashboard URL.
Constraints:
- Name matching is exact.
- The route only searches the authenticated user’s experiments.
Args: user: Authenticated user resolved from the API key. db: Active database session. experiment_name: Exact experiment name to resolve.
Returns: The matching experiment object with MCP context fields populated.
Raises:
HTTPException: Raised with 404 when no caller-owned experiment with
the requested name exists.
Authorizations
Path Parameters
Response
Successful Response
Represent an experiment with MCP-specific context metadata.
description and creation_date remain optional for compatibility
with legacy database rows.
Attributes:
description: Plain-text experiment description. Optional for legacy
rows that still store NULL.
creation_date: Experiment creation timestamp. Optional for legacy rows
that still store NULL.
context: Additional plain-text guidance for AI agents consuming the
experiment.
url: Dashboard URL for the experiment when available.