get_my_profile
View your current business profile that's being used to match contracts.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
workspace-alberta
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A4.2/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description clearly indicates a read operation ('View') and adds context about the profile's purpose ('being used to match contracts'). No annotations are provided, so the description carries the burden; it adequately discloses the non-destructive nature.
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 a single, front-loaded sentence with no wasted words. Every part adds value: the verb, resource, and contextual detail about contract matching.
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?
Given zero parameters and no output schema, the description is minimal but sufficient. It explains the tool's purpose and the profile's role in matching. However, it does not mention what fields are returned or if multiple profiles exist.
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?
No parameters exist, so the schema provides full coverage. The description adds meaning by explaining that the profile is current and used for contract matching, which goes beyond the empty 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 clearly states the action ('View') and the resource ('your current business profile'). It distinguishes from siblings like 'set_business_profile' (edit) and 'search_contracts' (different resource), providing a specific verb and resource.
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?
No explicit guidance on when to use this tool vs. alternatives. While the context implies it's for reading the profile currently used for matching, it does not mention related tools like 'set_business_profile' for editing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
B3.1/5.0
Disambiguation2/5
Many tools have overlapping purposes, e.g., multiple search/find tools (find_opportunities, find_matching_opportunities, search_opportunities, etc.) and detail retrieval tools (get_opportunity_details, get_alberta_opportunity_details, get_contract_details). This creates ambiguity for an agent to select the correct tool.
Naming Consistency4/5
Most tools follow a verb_noun convention in snake_case (e.g., search_contracts, watch_opportunity). Some deviations like bid_no_bid_scorecard use a multi-word verb, but overall the pattern is consistent.
Tool Count3/5
25 tools is on the higher side for this domain. While the number could be justified by the need to handle both federal and provincial opportunities, many tools are redundant, making the surface feel heavy.
Completeness4/5
Core workflows (search, get details, watch/unwatch, set/profile, analyze) are covered. Minor gaps exist, like no batch operations or tool to clear watchlist, but the surface is largely complete for contract tracking.