Skip to main content
Glama
Sign In
omnara

omnara

Official
by omnara-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Remote

List agent profiles

profiles_list
Read-onlyIdempotent

List a project's agent profiles with config summaries, filterable by name and sortable by name or timestamp. Use it to browse or page through profiles without fetching full definitions.

Instructions

Lists the project's agent profiles, newest first by default, filterable by name. Items include a summary of each profile's current config, not its full compiled definition.

Input Schema

NameRequiredDescriptionDefault
nameNoCase-insensitive glob over the list's logical name. `*` matches zero or more characters, `?` matches one character, and `\` escapes a wildcard.
sortNoSort order for named resources that expose created and modified timestamps.
limitNoMaximum number of items to return in one page.
orgIDYesOrganization ID (org_...).
cursorNoOpaque pagination cursor from a previous response's next_cursor. Omit for the first page.
projectIDYesProject ID (proj_...).
stats_sinceNoStart of the window `stats.usage` tallies, with `include_stats`. Omit to tally from the earliest recorded call.
include_statsNoInclude each profile's `stats`, so a list can show instance counts and usage without a request per profile.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.1
    • addedInput schema / properties / orgID / description
      Added value: +"Organization ID (org_...)."
    • addedInput schema / properties / projectID / description
      Added value: +"Project ID (proj_...)."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds useful domain context beyond annotations: default ordering is newest first, results can be filtered by name, and returned items contain config summaries rather than full compiled definitions.

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?

Two concise sentences that are front-loaded with the core action and then immediately clarify result scope. No sentence is wasted or repetitive.

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

Completeness4/5

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

For an eight-parameter list tool with full schema coverage and rich safety annotations, the description is mostly complete: it explains scope, default ordering, filtering, and return-content limits. It could mention pagination or the optional stats parameters, but those are covered adequately by the schema.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema documents all parameters. The description adds marginal value by noting name filtering and default newest-first ordering, but it does not add syntax, format, or interaction details beyond what the schema already provides.

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?

States a specific verb (Lists) and resource (the project's agent profiles), plus scope (project's) and default ordering (newest first). It does not explicitly name a sibling such as profiles_get or agents_list to distinguish itself, but the list-versus-single distinction is inherent.

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

Usage Guidelines3/5

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

Usage is implied: it describes what is listed and that it can be filtered by name, so an agent can infer this is for browsing project profiles. It does not state when to use this over profiles_get or agents_list, nor does it give any exclusions or alternatives.

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

Deploy Server

Other Tools