Skip to main content
Glama

query_response_artifact

Filter and retrieve stored provider API responses by artifact ID and environment, using pagination, fields, and text search to extract the exact data needed.

Instructions

Query a stored provider response with bounded, strict camelCase controls.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorNo
fieldsNo
filtersNo
describeNo
pageSizeNo
artifactIdYes
objectModeNo
textSearchNo
environmentYes
responsePathNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
shapeNo
responseNo
artifactIdYes
responseMetaYes
responsePathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv2.0.0
    • removedInput schema / properties / cursor / default
      Removed value: -null
    • removedInput schema / properties / fields / default
      Removed value: -null
    • removedInput schema / properties / filters / default
      Removed value: -null
    • removedInput schema / properties / objectMode / default
      Removed value: -null
    • removedInput schema / properties / responsePath / default
      Removed value: -null
    • removedInput schema / properties / textSearch / default
      Removed value: -null
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$defs": {
      +    "ArtifactQueryResponseMeta": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "complete": {
      +          "title": "Complete",
      +          "type": "boolean"
      +        },
      +        "contractVersion": {
      +          "const": 2,
      +          "title": "Contractversion",
      +          "type": "integer"
      +        },
      +        "fieldsResolved": {
      +          "anyOf": [
      +            {
      +              "additionalProperties": {
      +                "type": "integer"
      +              },
      +              "type": "object"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "default": null,
      +          "title": "Fieldsresolved"
      +        },
      +        "filtersApplied": {
      +          "anyOf": [
      +            {
      +              "items": {
      +                "additionalProperties": true,
      +                "type": "object"
      +              },
      +              "type": "array"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "default": null,
      +          "title": "Filtersapplied"
      +        },
      +        "inferredResponsePath": {
      +          "anyOf": [
      +            {
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "default": null,
      +          "title": "Inferredresponsepath"
      +        },
      +        "nextCursor": {
      +          "anyOf": [
      +            {
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "title": "Nextcursor"
      +        },
      +        "pageUnit": {
      +          "anyOf": [
      +            {
      +              "enum": [
      +                "items",
      +                "entries"
      +              ],
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "default": null,
      +          "title": "Pageunit"
      +        },
      +        "remainingCount": {
      +          "anyOf": [
      +            {
      +              "type": "integer"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "title": "Remainingcount"
      +        },
      +        "returnedCount": {
      +          "anyOf": [
      +            {
      +              "type": "integer"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "title": "Returnedcount"
      +        },
      +        "serializedBytes": {
      +          "minimum": 0,
      +          "title": "Serializedbytes",
      +          "type": "integer"
      +        },
      +        "sourceTruncated": {
      +          "anyOf": [
      +            {
      +              "type": "boolean"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "default": null,
      +          "title": "Sourcetruncated"
      +        },
      +        "totalCount": {
      +          "anyOf": [
      +            {
      +              "type": "integer"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "title": "Totalcount"
      +        },
      +        "truncated": {
      +          "title": "Truncated",
      +          "type": "boolean"
      +        },
      +        "truncationReason": {
      +          "anyOf": [
      +            {
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "title": "Truncationreason"
      +        },
      +        "warning": {
      +          "anyOf": [
      +            {
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "default": null,
      +          "title": "Warning"
      +        }
      +      },
      +      "required": [
      +        "contractVersion",
      +        "truncated",
      +        "complete",
      +        "truncationReason",
      +        "returnedCount",
      +        "totalCount",
      +        "remainingCount",
      +        "nextCursor",
      +        "serializedBytes"
      +      ],
      +      "title": "ArtifactQueryResponseMeta",
      +      "type": "object"
      +    }
      +  },
      +  "additionalProperties": false,
      +  "properties": {
      +    "artifactId": {
      +      "title": "Artifactid",
      +      "type": "string"
      +    },
      +    "response": {
      +      "anyOf": [
      +        {},
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Response"
      +    },
      +    "responseMeta": {
      +      "$ref": "#/$defs/ArtifactQueryResponseMeta"
      +    },
      +    "responsePath": {
      +      "title": "Responsepath",
      +      "type": "string"
      +    },
      +    "shape": {
      +      "anyOf": [
      +        {
      +          "additionalProperties": true,
      +          "type": "object"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Shape"
      +    }
      +  },
      +  "required": [
      +    "artifactId",
      +    "responsePath",
      +    "responseMeta"
      +  ],
      +  "title": "ArtifactQueryResult",
      +  "type": "object"
      +}
  2. Addedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden of behavioral disclosure. It only hints at 'bounded' behavior and 'strict camelCase' controls, but does not explicitly state that this is read-only, whether pagination is used, how artifacts are returned, or what side effects (if any) exist. This is too sparse for a tool with ten parameters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no filler, and the main verb and resource are front-loaded. However, the phrase 'bounded, strict camelCase controls' is jargon-heavy and could be clearer. It is concise but not optimally transparent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This tool has high complexity: ten parameters, no parameter descriptions, no annotations, and a specialized name. The description does not explain how to construct valid filters, what objectMode entries means, how responsePath interacts with the artifact, or when to set describe. An agent cannot reliably invoke this tool from the provided information.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for ten undocumented parameters. It does not describe artifactId, environment, cursor, fields, filters, describe, pageSize, objectMode, textSearch, or responsePath. The phrase 'strict camelCase controls' may hint at output naming conventions, but it does not map to any specific parameter meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Query a stored provider response'. This distinguishes it from most sibling tools, which are about connections, integrations, or proxying requests. However, it does not explicitly differentiate itself from closely related query-like tools, and the phrase 'bounded, strict camelCase controls' is vague.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance about when to use this tool versus alternatives such as proxy_request, download_provider_file, or get_connection_context. No context, prerequisites, or exclusions are provided, so an agent has to infer the appropriate use case from the name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.