Skip to main content
Glama

query_dci_remotecis

Query DCI remotecis (labs) using a flexible DSL with filters like name, tags, dates, and boolean logic. List all, count, or search with pagination.

Instructions

Lookup DCI remotecis with an advanced query language.

Listing all remotecis: To list all remotecis, use ilike(name,%) as the query.

The query language is based on this DSL:

eq(<field>,<value>) to lookup resources with a <field> having the value <value>.
IMPORTANT: Values must NOT be quoted. Use eq(name,dallas) not eq(name,'dallas').

You can use the comparison functions gt (greater than), ge (greater or equal),
lt (less than) or le (less or equal) using the same syntax as eq: <op>(<field>,<value>).

like(<field>,<value with percent>) and ilike(<field>,<value with percent>)
to lookup a field with a SQL glob like way. For example, to get the remotecis
with a specific name pattern, use like(name,dallas-%).

contains(<field>,<value1>,...) and not_contains(<field>,<value1>,...)
to lookup elements in an array. This is useful mainly for tags.

and(<op1>(...),<op2>(...)), or(<op1>(...),<op2>(...)) and not(<op>) allow
to build nested boolean queries.

null(<field>) to lookup resources with a field having a NULL value.

Here are all the fields of a DCI remoteci that can be used in the query:

- id: unique identifier

- name: name of the remoteci (lab)

- created_at: The creation timestamp. Use `today` tool to compute relative dates.

- updated_at: The last update timestamp. Use `today` tool to compute relative dates.

- tags: list of tags associated with the remoteci.

Listing all remotecis: To list all remotecis, use ilike(name,%) as the query.

Counting Remotecis: To get the total count of remotecis matching a query, set limit=1 and read the count field in the _meta section of the response.

Example for counting remotecis by name:

{
  "query": "eq(name,dallas)",
  "limit": 1,
  "offset": 0,
  "fields": []
}

This will return a response like:

{
  "remotecis": [],
  "_meta": {"count": 2},
  ...
}

The total count is 2 remotecis.

Returns: JSON string with list of remotecis and pagination info

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYessearch criteria (e.g., and(ilike(name,dallas),contains(tags,ga))). To list all, use ilike(name,%)
sortNoSort criteria-created_at
limitNoMaximum number of results to return for pagination (default 20, max 200). Use limit=1 to get count from metadata.
offsetNoOffset for pagination
fieldsNoList of fields to return. Fields are the one listed in the query description and responses. Must be specified as a list of strings. If empty, no fields are returned.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations are provided, so the description must handle behavioral disclosure. It explains the query syntax, fields, and output format (JSON with list and _meta). It doesn't mention authentication or error handling, but for a read-oriented query tool, this is adequate.

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

Conciseness5/5

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

The description is appropriately long for a complex query tool, well-structured with sections, examples, and bullet points. Every sentence adds value, and the most important information is front-loaded.

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

Completeness5/5

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

Given the tool's complexity (DSL, pagination, sorting, counting) and the presence of an output schema, the description covers all essential aspects: query language, fields, parameters, examples, and output format. It is complete for an agent to use correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already describes parameter types and defaults. The description adds significant value by explaining the query language, field usage, and providing examples, enriching parameter semantics beyond the schema.

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

Purpose5/5

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

The description opens with 'Lookup DCI remotecis with an advanced query language,' clearly stating the verb and resource. It differentiates from sibling tools like query_dci_components by focusing specifically on remotecis.

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

Usage Guidelines4/5

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

The description provides explicit examples for listing all remotecis, counting, and using the DSL. While it doesn't explicitly say when not to use it or compare to siblings, it gives clear context for its use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/redhat-community-ai-tools/dci-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server