[Feat]: passing call context to unauthenticated card modifier

Open
#657 7 comments 0 reactions 1 assignee View on GitHub

@ishymko is already working on this.

Since Jun 30, 2026.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
api, backend

Research direction

Look at the agent card modifier functions in the codebase, likely in a file handling agent endpoints or modifiers. Compare the signatures of regular and extended modifiers. The change involves adding a call context parameter to the regular modifier function. Check issue #647 for related work. Ensure backward compatibility by handling modifiers with one parameter. Test by modifying an agent card to use a dynamic request URL part.

Written by the indexing model from the issue text.

Description

component: core
Is your feature request related to a problem? Please describe.

We are wondering if support can be added for passing the call context to the regular agent card modifier, just as it is for the extended card modifier.

Describe the solution you'd like

Agent card modifiers should be given a second parameter for the call context, matching the signature of extended agent card modifiers.

Describe alternatives you've considered

We can construct our own Application and Adapter classes to override the get agent card endpoint handling, but this is cumbersome and hard to maintain.

Additional context

I guess we're also wondering if this is intentional - i.e. if agent cards should not depend on anything from the call context. In our case, we want to use part of the request URL (which is dynamic) as part of the url field in the response. Also, if we work to add support for this (like in #647), do we have to make the change backwards compatible and support modifiers that don't take in the call context (i.e. only have one parameter for the agent card to be modified)? I think anything goes as long as we're on the 0.X.Y versions (i.e. anything below 1.0), but just want to make sure.

As with #647 I am more than willing to lead development on this.

Code of Conduct
  • I agree to follow this project's Code of Conduct
Dominant language
Python
Stars
2.2k
Forks
496
Avg merge
1d 23h
Merged PRs (30d)
16

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from a2aproject/a2a-python

All issues in a2aproject/a2a-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.