Issue scoped, temporary cloud credentials (AWS and Azure)
timebound-iam has 3 tools with mixed quality. Tool naming is verb-forward and clear (grant_access, list_services, list_active_sessions). Descriptions are present and moderately detailed, though some lack specificity on when/why to use them. Input schemas are well-formed with types and descriptions for all parameters. However, output schemas are completely absent from the visible code, no documentation of what grant_access returns beyond a vague reference to 'credential_file in the response'. The grant_access tool lacks clarity on error conditions and recovery paths. Composition is reasonable: three focused tools with clear separation of concerns. Security consideration: credentials are handled server-side (stored in ~/.tiam/creds), not exposed as parameters, good practice.
Issue time-boxed, service-scoped temporary cloud credentials. The credential_file in the response contains env vars. Use them with: env $(cat <credential_file>) <command> Available services: aws: - s3 [read_only, full] - ec2 [read_only, full] - dynamodb [read_only, full] - lambda [read_only, full] - rds [read_only, full] azure: - storage [read_only, full] - keyvault [read_only, full] - cosmos [read_only, full] - sql [read_only, full] Levels: read_only, full TTL: 15m to 12h (e.g. 15m, 1h, 4h)
List all active (non-expired) temporary credential sessions across all providers.
List all cloud services available for temporary credential grants. Use this only if you need the full list — grant_access already includes available services in its description.
Output schemas not documented. No schema visible for grant_access response structure (what fields are in the credential_file? what format? are there error codes or status fields?). list_services and list_active_sessions return types also undocumented.
grant_access description uses example values ('15m, 1h, 4h') inline. Move to parameter constraints (regex or enum for duration format).
Error handling guidance missing. What happens if the TTL is invalid? If the service doesn't exist? If credential generation fails? Descriptions contain no recovery guidance (e.g., 'Try list_services() first to validate service names').
list_active_sessions description is too terse ('List all active (non-expired) temporary credential sessions across all providers'). Does not explain when to call it, what the output structure is, or how to use results downstream.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | C | 63 | 2026-07-28+ | v2 |
| 2026-03-09 | D | 59 | - | v1 |
No indication of which parameters are optional vs required. Is 'profile' on grant_access optional? The description says 'Optional profile name' but the JSON schema should indicate required=[...].