Skip to main content
Glama
conan-io

Conan MCP Server

Official
by conan-io

get_conan_profile

Retrieves Conan profile configuration for host and build environments. Use to check compiler, architecture, and build settings before listing packages.

Instructions

Get Conan profile configuration.

This tool should be called when the user mentions:
- Their platform (Windows, macOS, Linux)
- Their compiler (gcc, clang, msvc, etc.)
- Their architecture (x86_64, arm64, etc.)
- Build configurations
- When they want to list packages for their specific platform
- When they need context about their Conan environment
- When they want to check a specific profile configuration

This is typically a prerequisite step before listing packages or making 
platform-specific recommendations, as it provides essential context about
the user's build environment.

Args:
    profile: Optional profile name to retrieve. If not specified, retrieves the default profile.

Returns:
    Dictionary containing both host and build profile configurations.
    The dictionary structure includes:
    - "host": Host profile settings (compiler, arch, build_type, etc.)
    - "build": Build profile settings (compiler, arch, build_type, etc.)
    - Additional configuration like package_settings, options, tool_requires, etc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
profileNoSpecific profile name to retrieve. If not provided, uses the default profile.
Behavior4/5

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

No annotations provided, so the description carries full burden. It discloses the return structure (dictionary with host/build configs) and that it retrieves a profile. However, it does not mention potential failure modes (e.g., profile not found) or side effects, but these are minor for a simple getter.

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 well-structured with a lead sentence, use-case list, parameter doc, and return explanation. It is slightly verbose (the bullet list of triggers could be condensed) but still earns its content.

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 no output schema, the description fully explains the return dictionary structure. It also provides context on when and why to use the tool. The single optional parameter is well-documented, and the tool's role as a prerequisite is clear.

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 coverage is 100% and the parameter description in the schema is nearly identical to the one in the main description ('Optional profile name...'). The description adds no significant additional semantics beyond what the schema provides, so baseline 3 is appropriate.

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 clearly states 'Get Conan profile configuration,' a specific verb+resource. It distinguishes from siblings like list_conan_profiles by explaining it retrieves a specific profile (or default) and is a prerequisite for platform-specific operations.

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

Usage Guidelines5/5

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

Explicitly lists multiple trigger scenarios (platform, compiler, architecture, build configs, listing packages, environment context) and positions it as a prerequisite step. This provides clear guidance on when to use versus alternatives.

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/conan-io/conan-mcp'

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